I'm not exactly sure what this post details, but from what I understand, I think there's a big misunderstanding here on what the renderer actually does and why.

Dreamseeker does not process things it doesn't need to, because it doesn't have to. If there's nothing visually changing on your screen, there's no reason for it be drawing anything. Frames are just pictures after all. If nothing has changed, then it should be fine to keep it the same. This is why you're seeing very low to nill frames per second.

I suspect what's happening when your frame rate jumps is your recording software uses your CPU as a measuring stick - so to speak. So when you are really crunching some data, it skews the results that you're seeing in a way that aligns with 'high performance.'

The idea that Dreamseeker needs to constantly be drawing and redrawing everything on screen all the time is not the solution and quite frankly would be a very poor design choice. That would just mean needless overhead for the client for no noticeable gain.