Sorry, but I’m confused about what you’re saying here.
There are zwave manufacturers who are currently offering switches that support double tap, triple tap, etc. And they do work with SmartThings now. 
Basic Concept: Tap patterns are converted by custom DTHs to button pressed events
In all cases, the different tap codes are presented as different buttons being pressed, like a regular button controller, and that’s how You can use them with smartlighting or webcore or a smartapp. The DTH does the heavy lifting of changing the information received from the device into a button number and then telling smartthings that that particular button was “pressed.” Like a double tap on the top of the rocker might be presented as button three, and a double tap on the bottom of the rocker be presented as button four.
There are no lag issues because it’s the device itself that captures the initial Pattern before anything is sent to the hub.
There are two different ways that this is being done.
Method 1: Central Scene Commands
The homeseer switches do it with the central scene command. The device captures the tap pattern and then send a scene number to the hub. The DTH gets the scene number and converts that to a button controller Event like “button four pressed.”
Method 2: Association Groups
The GE switches do it with association groups. Again, the device captures the tap pattern, but then uses association groups to send out a basic message. The hub will receive it if it is in the correct association group and again, the DTH converts it to a button press event.
There are custom DTHs already in the forum for these devices if you want to see exactly how it works.
There’s no need for the platform to add anything to process the information from these two methods. Unless you want to do it without the custom DTHs.