The fingerprint is just used to pick the best-match driver when pairing. You can always manually change the driver afterwards (just like you did now to temporarily switch to the "Device" driver). It is, of course, a better end-user experience if the driver matches as-is, but if the fingerprints are truly the exact same, I don't know what else you could do.
Except...what kind of devices are these? I saw "Swidget" above somewhere, so I don't know if that's what you're talking about, but if all the devices are laregly the same except for a capability or two (and they have a lot in common otherwise), you could do a parent/child thing--the parent device handles all Zigbee communication, but child/component devices can expose the relevant capabilities to Hubitat, which you can dynamically create/remove (and use different drivers for, with different capabilities) as needed.
On the Z-Wave side, one example of this is HomeSeer's Flex Sensor. The parent driver handles temperature readings, which is all the device supports as-is. Optionally, the user can connect either a light/LED sensor or a water sensor, and the parent driver will create either a switch (read-only, to indicate whether the LED is on or off) or water/moisture sensor child device for use with those components, if needed.