How many users?

If xchars isup and running, thn console loop is simple a message dispatcher.  It is perfectly reasonable for users to jump in and out of a single console manager, but easier still to start you own loop,  and grab a shared segment with the previous.

As long as everyone, especially exec commnd, acn format a proper linux command, then multiple users are fine with one console, and the console run as a server in client server.

Or, if your processor supports multiple keyboards and folks can share a screen, or another monitor; console won't care, neither should most snippets.   If a snippet is concerned, then grab a reserve, name segment on args and,use that with your clients. Or, it your snippet is a tightly binding utility, like a math solver, then  it should be tightly bound to application snippet.

Tightly bound means they go directly to each others interface, bypass exec command, and likely have a shared segment. Games, they are characterized by a high speed io controller with multiple inputs, tightly bound to a qt loadable wayland machine.

We have 64 bits of address space, let us enjoy it. Use the args space, the hardware side of namespaces. I graphics, take a chunk of args, reserve it for the frame buffer, let multiple wayland machines have a go at one frame, that should be interesting.  Each of the machines in competition, the players allocated a frame buffer and an over lay mask.  They signal the frame buffer snippit, and their portion of args list becomes part of the light show.  The model is so simple, an array of 64 bit words, addressable by a 64 bit address. In the same address space, the two parties simple agree on the structure of their portion on args list; and all agree on the format of a linux command.