I think anything that is joystick would work just well on hidraw. Even compositing devices with the first interface joystick would be OK. So far I'm using all my devices via the hidraw backend, without any issues. This includes pedals, shifter, FFB (HID-PID) wheel, joystick, rudder pedals, etc. - with all their features properly utilized via the controlling software.
On other side FFB devices not compatible with HID-PID specification (which use separate FFB drivers) need to be assigned to the SDL backend. IMO using the registry for whitelisting (or blacklisting) vid, pid pairs to the respective backends is one possible solution. Better if this can be done visually in the control panel.
Proton's implementation is really good with the hidraw prioritized over SDL. Just the hardcoded vid, pid pairs aren't user friendly IMO.
What is a real problem in the bus_udev implementation is the evdev backend, which enumerates mouse and keyboard devices in addition to the other devices. Especially keyboards are added with empty reports, without any usages as they have only keys, while the evdev backend searches for buttons. Then any keypress crashes the winedevice.exe, etc.
IMO the evdev backend should be disabled through DisableInput by default, so when the device is unavailable via hidraw, the next choice to be SDL.