How does it know which threads are UI threads?

I think it should at least know which thread handles mouse movement.

Won't help if the problem is as the author describes (contention for a system-wide lock).

I think the windows scheduler might already do this, but the issue is that UI message queues take a highly contended lock.