Fullscreen simply hides away the frame window and runs the regular fullscreen, so I'm not sure if that's something on my part or a more general Windows quirk.
There is in-progress work to make the DLL spawn a secondary thread instead of a separate process (which fixes oddities related to that), but that involves rewriting entirety of the code so may take a bit before it's out.