>I recently tried to set up Fedora running a VNC or RDP server, and after a couple of days of futzing I gave up. I guess Wayland has managed to regress on that from where X was a decade ago?

According the Wayland FAQ [1] they have specifically avoided defining a remote API.

[Q]: Is Wayland network transparent / does it support remote rendering?

[A]: No, that is outside the scope of Wayland. To support remote rendering you need to define a rendering API, which is something I've been very careful to avoid doing. The reason Wayland is so simple and feasible at all is that I'm sidestepping this big task and pushing it to the clients. It's an interesting challenge, a very big task and it's hard to get right, but essentially orthogonal to what Wayland tries to achieve.

Which leaves you using Spice, or older solutions like X+VNC. Check out Apache's incubator project Guacamole [2] if you'd like a solution that can stream a Linux or Windows desktop to a browser via HTML 5; it supports SSH, Telnet, RDP and VNC. And despite supporting those older protocols it integrates with LDAP or CAS [3] for external authentication along with DUO for two-factor authentication.

[1] https://wayland.freedesktop.org/faq.html#heading_toc_j_8

[2] https://guacamole.incubator.apache.org/

[3] https://en.wikipedia.org/wiki/Central_Authentication_Service

N.B.: I added the Q and A tags to the Wayland FAQ quotes for clarification which is why they're highlight differently from the copied text.