This is really unfortunate. "Fortunately" it seems to be a result of the simulation engine using only a single core- there is the opportunity for the developers to get a 2-8x speedup from switching to a multithreaded simulation engine.
I imagine there's fairly loose coupling between, for instance, fluid calculations, biter pathing, and on-belt entities, which tend to require dedicated strategies for mitigating their outsized performance impacts. (to include using console commands to simply delete the biters) Those sound like fairly low hanging fruit for splitting off into three threads if there's no plan to completely multi-threadify the sim engine.