This is where you start making design decisions.
It sounds to me like you’ve already got your “end-points” sorted and so your enhancement is basically adding the “smooth segue” component.
If this is the case then simply adding a Black Init stage (which is what your patch is saved as) gets you off the mark
Your patch will likely involve running the transition then “storing” the end state(s) for the next segue.
This is now easier within one MH with virtual mappings courtesy of 1.14Beta, but you could also do it with two MHs talking to eachother (if you have the spare I/Os) – if you haven’t migrated either of your boxes yet.
Another thing I’m thinking about is speed of transitions but this can be V2!
Looking forward to seeing what you do!
PS. In some ways, this is reminiscent of my FluidTransitions patch described here
Yours can be simpler as that was designed to be very general.
On the other hand, yours will likely have the complexity of more than one 1-shot-Saw
(NB The FluidTransitions loopback patch will look a bit different in Virtual Mapping world – awaiting formal release before I re-write 
)
btw, I typically opt for [0:127] (Depth = 64) LFOs with this kind of design, then maybe an Equalizer stage, then A Rescale stage. The Rescale pipe holds your mapped Before-After states