This is the root cause for what you’re experiencing, and isn’t improved by any Wayland protocol support. It has entirely to do with the implicit sync stack that exists within Xwayland and nVidia’s lack of support for implicit sync entirely. nVidia proposed an explicit sync method in another merge request that was shot down by the X devs as they “don’t solve anything for the Mesa driver” by supporting explicit sync as a concept. Explicit sync is a concept that has less of a performance penalty, and other vendors support the notion of switching to it, but nVidia’s hostile relationship with the X developers and FOSS as a whole has caused roadblocks at present where the projects don’t wish to collaborate with nVidia’s proposals.
So to summarize, this is exclusively an Xwayland issue, nVidia and the developers have disagreed as to how to proceed, and neither side shows any signs of flinching. nVidia is hard nosed about implicit sync and refuses to implement it in their driver for various reasons, and the Xwayland devs are being hard nosed and absolutely refuse to accept nVidia’s merge requests for adding explicit sync support for reasons relating to what I can tell is basically “bad blood” between the groups. Even if the project accepts explicit sync, nVidia still has to add the feature to their release pipeline, which would put it past the 545 release some months down the road. Again, even if everyone agreed effective today, we still wouldn’t see resolution on this until early 2024 at the soonest. Xwayland will remain broken for nVidia users basically for all time, at the present rate of development. Our applications will all be ported to Wayland before this gets fixed.
Sorry for the soapbox moment, but, it has been incredibly frustrating to see this all play out.