I am more concerned with the cursor freezing once in a while when the system is under load. This should never happen, but does.

It is solvable by a combination of the following:

- Leveraging priority classes: Wayland compositor should be SCHED_RR instead of SCHED_OTHER, and benefit from posix realtime scheduling and thus PREEMPT_RT if present.

- Leveraging hardware acceleration: Use a hardware sprite.

As far as I am aware, kwin does neither.

Whereas my Amiga 500, or even a 1985 A1000, kinda does both: Preemptable round robin scheduling is the default with the input server that handles the cursor having high priority, cursor is the first hardware sprite.