This is not a helpful meme. If your preferred desktop environment drops X11, then you are de facto "forced" into one of four options:

1. Fork it.
2. Switch to a different DE.
3. Switch to Wayland.
4. Stop using a GUI on Linux.

For most Linux end users, (1) is not a realistic option (DEs are far too complex for one individual to maintain a fork indefinitely) and (2) gets less and less realistic with each passing year (as DEs drop X11 support). (4) is probably feasible for a lot of users (they can switch to Windows or another OS), but not a particularly helpful answer. That leaves us with (3).

It is worth acknowledging that this software is maintained by volunteers. Framing it as being "forced into Wayland" is a somewhat one-sided way of putting things. But that does not make it altogether inaccurate. End users are justifiably frustrated when functionality is removed for "architectural" or infrastructure reasons, rather than because the functionality is actually problematic in some way. Many DEs have actively removed most of their keyboard settings, usually because they were using the X server as a backend for those settings, and whatever Wayland compositor they switched to lacks feature parity with X (and/or because nobody could be bothered to explore the compositor's API surfaces and find equivalent knobs). It is unfair when Wayland gets blamed for those DE failures, but from the users' perspective, everything was fine until Wayland showed up.