Just to clarify, I'm assuming you have configured double-tap to set the dim level of the same HS-WD100+ switch, and triple-tap is configured to set the dim level of other non-HomeSeer switches? Otherwise, as @dalec mentioned, this is a function of the device and device handler for the HomeSeer switch, since double-tap and triple-tap should behave the same for the same actions.
Unfortunately, while the HomeSeer dimmers support configuration options to set the dim rate when controlled manually at the switch - and it would be easy to add a preference for this to the device handler, the HomeSeer dimmers do not appear to support a configuration parameter for controlling the dim rate when set externally. I was hoping my HomeSeer controller would show this as an undocumented feature when paired with the switch, but it only shows the documented local control dim rate options.
This is disappointing as even the GE dimmers support this basic capability. Dim rate control really belongs on the device itself for many reasons, and the only other option would be to modify the device handler to track the dim level and attempt to send multiple intermediate dim commands. This adds a lot of normally unnecessary complexity to the device handler, and I'm afraid added cloud latency might make this almost unworkable.
I'll keep thinking on it though - and maybe relook at the handler. I believe this quick ramp-up behavior could be causing issues I've seen with some LED bulbs. A simple(?) mod the device handler to provide an option to allow just a couple of incremental dim levels might workaround this LED bulb issue I've seen as well. I'll also ping HomeSeer to see if there is a chance they will be upgrading the firmware at some point to support this. If anyone has any other suggestions, please let me know,