the reason for orion_uk to know is, he spent much time to perform dozens of test -
big thanks for that 
- with a failing scene that never rendered past 100-200 frames for him, and just had 4000 frames successfully rendered (during ~ 1.5days). since this didn't ever happen on my machine, i can only guess it is connected to gpu use for system also - since it was octane that just stalls at random points - and i have dedicated gpus on my machine, so this might make the difference.
after changing the command sequence when doing frame forwards, by removing some explicit pause and restart commands (letting octane just restart because of the changes only), it did clearly work for him. imo the difference between never get past 5% of the animation in every previous try and now having 100% without interruptiion is a very good sign, that this solution will work, and will hopefully work for everyone else also.
regarding the other thing: can you please try if deactivating live geometry before loading helps? it seems to resolve this for everyone else having this problem, so it'd be good to know...