Systemd and Wayland are very different pieces of software. It's easy to imagine (in fact I think it's very common) that end-users of Systemd just use it to launch a service which replaces all the logical features of Systemd. (E.g. for an extreme example, a kubernetes cluster.) If systemd doesn't support some feature, it's really fine. Maybe even preferable. You can get it working by some other means.
Wayland on the other hand, it really does need to do everything well. If Zoom won't run in Wayland, needing to launch X11 to run Zoom means Wayland is broken.
Zoom is an awful piece of malware. Wayland doesn't need to support zoom, zoom needs to support wayland. With that logic literally every change to an OS is broken because it doesn't run my cli accounting program from 1985.
Wayland on the other hand, it really does need to do everything well. If Zoom won't run in Wayland, needing to launch X11 to run Zoom means Wayland is broken.