We can also do this - the binding supports such a system, but I’m against doing this unless it’s really needed as it then must be maintained. I don’t think this situation really warrants having a static thing type defined since as far as I can tell it is perfectly usable as it is - just use a switch item only - the binding will work fine like this.
The automatic detection of devices is much nicer with many advantages for both maintainers, and users. Users can simply use ANY new device that turns up (so long as the device is of a type that the binding supports, and it correctly reports its services, which most do) - there are no binding changes required, unlike the ZWave binding which MUST be updated to support a new device at all.
I would have also written the ZWave binding like this if it was possible at the time I wrote that binding. Unfortunately dynamic generation of things was only added a year or two after the ZWave binding was written, and it’s quite a large rewrite to now do this (although it’s on my list of things to do one day!).