>the problem with Wayland is that one can't just 'switch' from X.
Does switching to a wayland compositor by default and using xwayland for the applications that still can't talk to it not sufficiently address that? At least as practically as is possible when replacing a popular piece of interoperable software with a large user install base?
Indeed, but the problem with Wayland is that one can't just 'switch' from X. Wayland provides graphics multiplexing; that's it.
Possibly mangled analogy: it's like saying we're switching from a LAMP stack to Postgres; it doesn't make sense as a statement.