Note that this also loses the synchronous processing, if the clipping thread is the foreground thread. I'm not sure it's critical, and I'd be keen to try without it. If it proves problematic, then we could have a path where wineserver instructs NtUserClipCursor to call the driver directly. If it still feels risky I can also probably try to have it in Proton for a while first.