I don't think evdev should enumerate mouse and keyboard devices at all, that's probably because you've configured your system with your user in the `input` group. It is not usually the distribution default, as it introduces a potential security problem where any process could then read the mouse and keyboard input without any access control from the X server.
Yes, this happens only with a user, which is a member of the 'input' group. I use a limited account, where the input devices aren't enumerated by bus_udev.
Anyway, would be good if the evdev backend is not the first choice if hidraw is unavailable due to lack of permissions, etc.
I'd like to ask you how to proceed with a MR which includes mostly work on winebus.sys, but there is also some initial work on wineusb.sys. It's an implementation of IOCTL_HID_GET_INDEXED_STRING, and the later work depends (at least logically) on the changes of wineusb.sys. Sorry for asking here!