If you want a really great approach to noise gating, a fixed threshold is fine but it works better when you apply it to the difference of two envelope followers - one with a short attack, long release (tracks input) and long attack, short release (tracks noise floor). Takes a bit to set it up, but it's a stupid simple way to get extremely effective gating and is easy to fine tune for your application. A lot of Voice Activity Detection (VAD) works this way; it's just a matter of tuning the coefficients and thresholds for your input.
Also useful reference for envelope following are the DAFX text [2], Will Pirkle's textbook on audio in C++ [3] and Zölzer's text [4]
[1] https://github.com/m-hilgendorf/rusty-compressor
[2] https://www.amazon.com/DAFX-Digital-Effects-Udo-Z%C3%B6lzer/...
[3] https://www.amazon.com/Designing-Audio-Effect-Plugins-C/dp/1...
[4] https://www.amazon.com/Digital-Audio-Signal-Processing-Z%C3%...
(pdfs can be found around the internet)
Bitwig gives you no access to their DSP technology in its scripting language, so it is not remotely comparable to Max in that regard.
Max, on the other hand, gives you no access to Ableton's UI or API.
I have both, but prefer Bitwig. But there is nothing out there quite like Max. Not even Reaktor covers the same territory.
I am hoping that the next big thing in Bitwig will be to open up their DSP API, and give us the ability to create our own Grid modules, and, beyond that even, our own native instruments and effects. But I do not believe that extending their Javascript API is the way to do this.
That said mixing DSP + UI is hard, and if you want to make the scripting user accessible it makes sense to keep them totally divorced.