Yes, this behavior can be related to the fact that currently the rendering is in pause, but not the Octane scene update code (this is why once you release the pause button, the scene is updated to the current state).
I could add a new feature to the IPR to stop the Octane scene update: one pause button for rendering, and one pause button to scene update. Can be even useful to render something in the background while you are working in the scene without update the scene in each user action.
I will think about it for the next release.
Computer Graphics Software Developer
Octane plugin development and support: LightWave and Houdini