Hell, I could switch tasks with every tick of the CPU clock if I wanted to. Every system related task would be uber-snappy as a result. Any actual usespace program would run like crap though.
Do you have any idea how a modern pre-emptive scheduler works? If some thread needs to access the disk, it should be preempted (can not run). No matter how fast you make the rest of the system, you have a bottleneck that exists for that given thread, that you can NOT solve in S/W.Obviously some people think jitter is "disk-io". If you have reduced "disk-io" with there being the same disk i/o, you know jitter is lower. (lol)
You are the worst type of developer: One who makes changes, convinced he is right, without testing every possible outcome. Then when people tells him the downsides to his approach, he ignores them. And when people start to tell him he outright breaks stuff, he laughs at them. Then people like me get paid to clean up the mess you leave behind.