slaving VST settings?

Maybe this is an old idea and someone can point me to an existing FR, but... I would love to slave all (or some?) of the settings of a given VST to another instance of that VST. I know about parameter modulation, but it's not practical for this scale (unless i'm missing something). This comes up all the time when I have an instrument recorded with multiple tracks: say a guitar amp with a stereo pair, a distant mic, a room mic, etc. The tracks live in folders with VSTs instantiated at different levels and are contained in a top-level "guitar1" folder. I then duplicate the entirety of those tracks for "guitar2" which plays a different take. If I go in and change the VSTs for guitar1, I don't want to have to go in and repeat all those changes all the time for "guitar2". Even deleting/copying/pasting the VSTs from one to the other is a pain. Other slaving, like setting the entire FX chain of a given track to be slaved to another -- for both the settings of the plugins and which plugins are instantiated -- would be similarly useful. Thoughts?

I would use it!

I suppose "slave" is probably the wrong term -- I'd be satisfied with a bi-drectional lock (slaving seems more involved; where changes are passed in only one direction.) I'm sure there are a few things to sort out (e.g. how parameter modulation would be sorted out) but it seems simple enough overall, and would be really handy.

I made a FR: Please vote. Anyone else think this would be useful?

Voted! It would be a time-saver in many scenarios, as a kind of "meta-parameter modulation". Good idea!