Well.. , I do now.
The speed is a '3 on the tree' transmission with no clutch, no throttle. Always an aggravation.
I reduce mouse sensitivity somewhat. Enough so that I can move to each bottleneck relatively quickly, follow planes, yet hopefully be able to mouse view right to left without incurring skips in position. Which you would normally want in gaming, no lag movement. Reducing sensitivity farther would guarantee smooth left to right but you lose speed in following the action in general, being in the right place at the right time. I attempt to compensate a medium high sensitivity with a lenience on keyboard and acquired skill.
In other words, minimizing skips in speed transition (changing a gear with no clutch) is compensated by changing my view , I may spin around them and capture from a different angle, or set up for the next shot. I also have inserted small visual tricks such as a slow 'mouse up' at the same time you shift from walk to run. The motion hides the speed change and it looks fluid even though it isn't.
There is going to be edit. No one want to watch a free cam spin around looking for possibilities on the map. I reduce this usually with a second pc and an enlarged map to glance which will guide me to the hot spots. Edit, for me is more a process of opening the package to see if anything is there. I'll tag scenes with maybe 1sec extra at each end point for transition insertion and move on.