The SNAP action has been in clyphx for quite some time (though it got enhanced significantly a while back when it started to also cover DrumRack send levels). The EnvCap action though is very recent. So you haven't missed it for long
What I use?
Yeah the Snap action for sure. Ever since the above mentioned update came, I used it for changing my drum kits on the fly including their drum send levels.
I rack all my hits up as 128s in racked Samplers, so that each new kit is just another setting of my DrumRack, which is now in my default template and my Snap clips are the in-set kit chooser.
The quantized morphed change is very nice with this too. You should also look into the Snap rack that comes with Macrobat (included). That allows you to morph between two Snaps via turning a Macro/encoder. (Though that is more useful when you don't involve the SampleSelector, as that one obviously jumps from one sample to the other since it can't morph between them).
Generally Macrobat is something I use quite a lot. Especially the receiver rack and the track rack. (the later for instance allows you to control all 12 track send levels from Push, because I make the nK track rack control sends 7-12 and I have control of that rack in Pushs device mode.
But I also often use x-controls to give my Midi controllers functions they otherwise couldn't have. (something as basic as "lock control surface to device" is very useful for instance)
All'n all I almost use it out of habit though for almost anything. If I come up with a problem I want to solve, my first look is always into the clyphx manual to see what clyphx has to offer. Often that is also the last step, because either clyphx has a very elegant solution, or none exists.
(That changed a little for me though lately since I acquired Bomes MT - because that can do things that clyphx alone couldn't. But both work very well together)
For anything that clyphx can do, I would
NEVER look further into using M4L, since the solutions are often rather similar (they use the same Live API after all), and while just loading M4L uses up quite a bit of CPU and introduces stability issues, clyphx has no discernible CPU footprint to speak off and the very few times it does crash, it doesn't take Live with it.
Of course there are vast areas of things that M4L can do that clyphx can't, but for those I usually have Vst solutions instead.
The only thing missing in clyphx that should be possible for it are more time based triggers (Think fades, not quantization). It has the BPM Ramp action, but that is unfortunately the only parameter that can be changed in this manner. For me simple automated fades of send levels or other parameters would be the cherry on top of that delicious clyphx Sunday though