Shows you do not have the faintest idea what Wayland (and X11 for that matter) are. A computer is not a dumb tv. The “display server” is not just displaying, it is orchestrating the input flow to apps, and orchestrating the output flow (display but also sound) apps emit in response to this output. It’s not just about producing the perfect display, it’s about producing the perfect display in response to user input.

One of the main reasons X11 had to be abandoned, back when Wayland was codenamed X12, for example, was that the X11 core protocol allocated a single byte for key codes which broke in a major way when globalization and multimedia keys became a thing and HID could not be shoved into the legacy protocol (you could, exactly like for legacy 8bit encodings, try to define custom mappings that hopefully dropped enough parts to fit). And then you had the unpleasant malware reality where you really did not want any random app spying on the input provided to the banking app.

Wayland is all about trying to untangle legacy output *and* input, when the general co-mingling baked into X11 could not cope with new realities. Unfortunately some of the untangling is not finished yet.