It's probably more like, "let's lock ourselves into an early design decision that makes it hard to expose input remapping without realizing that's what we're doing because the architecture looked so much cleverer that way".

The OP isn't asking for some beautifully engineered UX with GUI that walks you through every possible disability modification. He's more than happy to go through a long procedure [1], as on Linux, to get that memory block to point to a different address. He just wants it to be exposed at all.

Others have claimed that this is some kind of full-featured thing. Well, as best I can tell, his Linux workaround just involves xinput and lsusb, both of which are available on Alpine Linux, the ultra-minimal distro.

[1] https://shkspr.mobi/blog/2018/05/using-the-evoluent-vmcr-c-s...