The question is what is native support for Wayland? Wayland Compositors are so fragmented how could they possibly support the multitude of environments?
Wayland is a protocol that at least in theory should be implemented very similarly by all available compositors.
Of course in practice there will be differences, but they shouldn't be large.
The idea about a standard is that all implementors adhere to it, except for very good reasons. Style and proprietary features are not covered for example. Compositors could also differ in which extensions they support. But the core behavior should be the same and applications should not have to care.
The problem is that you can't realistically do anything with just the base protocol. Everything relevant beyond setting up buffers and surfaces happen in extensions.
Unfortunately I've run into this a lot on modern machines. I wanted to port some of my GTK apps over to Wayland, but I can't easily do that since non-GNOME Wayland desktops don't render it properly. The fragmentation in Wayland implementations is real, and can hurt you.