Feature proposal: Add option "sticky" to safety sw

Hi to all, and thanks for the amazing firmware.
@PB: if you ever decide to accept donations let me know.

I know, it's possible to implement a "sticky throttlehold" with virtchannel like this:
=============
[channel3]
safetysw=Virt2
safetyval=-100

[virtchan2]
template=complex
[mixer]
src=Virt2
dest=Virt2
usetrim=0
curvetype=min/max
points=0
[mixer]
src=Ch3
dest=Virt2
offset=-1
usetrim=0
muxtype=add
[mixer]
src=AIL
dest=Virt2
switch=HOLD1
usetrim=0
curvetype=fixed
================

Now I am thinking if it would be possible to implement that feature in deviation itself,
which would make it easier for the user to config.

The logic would be simple:
after safetysw has been flipped and switched back to normal.
- keep the channeloutput at safetyval until the result of all applied mixers = safetyval

There could be a new option like this:
[channel3]
safetysw=RUD DR1
safetyval=-100
safetysticky=yes

What do you think?

I agree with FDR, I have Sticky TH on some smaller models, but for larger 600+ Helis en especially Nitro driven helis and planes you have a few engine cut options, ie. Cut to idle and Kill the engine.

I believe the current flexibility allows one to implement all these variants with relative ease.

Ok, there are situations where you don't want "sticky TH"
That`s why I proposed it as an option, where you can have either:
====================
[channel3]
safetysw=RUD DR1
safetyval=-100
safetysticky=yes
==== or as it is now =====
[channel3]
safetysw=RUD DR1
safetyval=-100
==========================

So it's still the user who decides which behavior he wants.
The only downside I can see is the risc of introducing bugs,
besides the development effort that might not be worth it.