I still use X forwarding.
It works just fine using xWayland, and X forwarding has always been so janky there is no chance to notice any difference caused from using xWayland instead of native.
It will surely take many years and well established wayland native remote tunneling before anyone thinks of ditching xWayland.
At least those eat no resources besides taking up space in htop. And can be traced to the parent being weird.
Have you dealt with io-locked processes? Funny D-statuses spreading like a disease, anything that touches an infected process or resource also inherits it. Worst cases I have seen (nfs client kernel module not connecting a mountpoint properly) made every one of those fully resistant to -9.