Editor camera stutters/does not process inputs

Keys held are sometimes ignored or processed half a second later when controlling the editor camera, it can show up on every other input or won't for multiple minutes.
Sampling inputs through 'Input.IsKeyDown' in a game build works as expected.

Mouse inputs seems to suffer as well, seemingly missing frames or inputs when rotating the camera.
I fiddled with the editor camera's input-handling code (removing cases where it would exit out before hitting 'UpdateCameraAsPerspective'), I forced the camera to rotate automatically by increasing it's yaw inside the function mentioned before and capturing a video of it next to my moving cursor, there were indeed frames (sometimes up to 6 in a row) captured where the camera wouldn't rotate but the windows cursor would move. The video captured was at 60fps, I couldn't find the editor view's framerate since RivaTuner flickers for some reason( perhaps related to the view implementation inside wpf? ) but if it is vsynced it would probably be at 144hz to follow my screen's refresh rate ?

While capturing the video through OBS, my gpu and cpu where under minimal load, rivatuner wasn't running and my web browser was idle.
When running a single camera build of the animation sample RivaTuner reported ~900 fps so it's unlikely that performances are a concern.

Is something wrong with how the camera 'MicroThread' created through 'Game.Script.AddTask' is scheduled in editor ?

Is this issue on my end only ?

Start by reproducing the stutter in the editor camera and compare it with the animation sample game build, where Input.IsKeyDown behaves normally. Read the editor camera input handling around UpdateCameraAsPerspective and the microthread created through Game.Script.AddTask. Done means identifying the scheduling or input-processing cause and confirming smooth keyboard and mouse camera input.