Hey, well.. your going to laugh or cry when you hear my solution.. but it does work! I ran into the same problem you did.. here's what I found.
I found if you put another render driver inside your custom ROP OTL it gets run when you hit that OTLrender button. So I put a dummy chop network and a dummy channel output driver inside my otl. The chop network just has one dummy constant channel defined and the channel output driver points to that so it doesn't error out.
The channel output driver gets run when the top render button is run.. so I put this in there
CHOP PATH: ../chop/dummy (this points to my dummy channel)
OUTPUT FILE : /dev/null (might need to be something else on windows)
Pre-Render script:
source opdef

Driver/myOTL?jumpstart.cmd `opfullpath(“..”)`;
So that's the trick.. in the pre-render cmd it calls a script inside your otl to get things going. Quite hacky I know… The dummy channels and such is just so the channel driver doesn't error out and executes the pre-command
I think I had found another soulution that was less hacky but it only seemed to work when you “hit” the render button.. it didn't work when you ran “render myOTL” from hscript.. so I went for this solution
d