I can't find the story you're talking about here, but one thing that would be good to understand here is whether this is some flaw in the Wayland protocol, or whether this is an implementation issue in a specific Wayland compositor like Gnome's Mutter. People tend to blame a lot of issues resulting from immature implementations on some unspecified "Wayland" (whatever that means).
All I can find is that in the past Mutter had lower latency for its Wayland implementation when compared to it using X.org, but it seems that Mutter's latency story has always been iffy in the past. FWIW it seems that Sway for example has finely grained input latency tweaks built in while being Wayland compliant [1].
All I can find is that in the past Mutter had lower latency for its Wayland implementation when compared to it using X.org, but it seems that Mutter's latency story has always been iffy in the past. FWIW it seems that Sway for example has finely grained input latency tweaks built in while being Wayland compliant [1].
[1]: https://github.com/swaywm/sway/releases/tag/1.4