What we've been told by staff (Mike, who wrote the built-in driver) is that the hardware itself doesn't send different events for multi-taps, so that's all done with software on the Bridge side of things. (Loooking at the API, that seems reasonable to me--looks like there's a "rule" that resets the press count after a few seconds, and probably something that increments it after each time that I didn't bother looking for...)
There's no reason you couldn't do something similar on Hubitat with a rule or custom app. For example, you could track the current "push count" in a rule and do a different action depending on the current value. For only two taps, you could use a rule's built-in Private Boolean to easily track two states:
IF (Private Boolean is True) THEN
Do single-tap action
Set Private Boolean False
Wait for event: elapsed time: 0:10:00
Set Private Boolean True
ELSE
Do double-tap action
Set Private Boolean True
END-IF
The one thing I'd note is that you'd want to give Hubitat a fraction of a second (at least) between taps to "save" the variable values so they're correct the next time you tap the button, which will wake the app/rule. Hue does this very fast, perhaps because it uses a smaller and simpler data storage mechanism, but Hubitat might take a couple hundred milliseconds or so--so don't mash the buttons together super-quickly (but you shouldn't need to wait incredibly long, either).
Alternatively, I wrote a custom app to emulate Hue Dimmer-type behavior on Hubitat, letting you use multi-taps for buttons that don't "natively" support them: