Just to give you a hint here, this *really* isn't what vRA was designed to do. Of course, you can still do it, but you're:
- In for a long haul if you're new to vRA and vRO (don't call it "vOrch")
- Will require vRA
- Will require extensive vRO coding of custom workflows and reuse of existing workflows
I'm aware that there is a long haul ahead with lots of learning required.
I see your point, this might be trying to make vRA do what it was not intended to do.
I'm guessing that this whole process belongs in a vRO workflow. Time to start coding some custom workflows...
We do some similar template management in our environment. We do it with a mix of vRO and vRA. Without fully understanding your environment its tough for me to offer up advice on what to use and where. I'll say that most of the work was in vRO for our solution.