I’d find that annoying too. My first thought to avoid the proliferation of ProxyVMs would be to change the .conf file and restart the ProxyVM. Do you think that has a chance to work?
Not related to Mullvad, a note on my Fieldnotes and a heads up on how I'm thinking about creating vs configuring VMs (in progress!)
Unrelated to that, while the notes you’re reading remain valid (I wrote them, in case it’s not obvious), please note that if you find yourself writing complicated Jinja files I’d recommend you to take a step back and shout here (you can ping me directly).
The reason for that is that since I wrote my notes, I’ve started thinking that it is often best (from a maintainer’s perspective) to separate the VM creation from the VM configuration in the Salt formulas. And a lot of the complexity in my experience tends to appear when trying to make the VM creation steps configurable by the end user. (You might not be there, but that’s the point of this heads up, that you can recognize when you get there. 
)
I’m in the process of validating the work flow before updating my notes. (Don’t hold your breath, and please don’t stop what you’re doing; it’ll take time for me to write down everything, so keep going, and watch for complexity. A lot of complexity involving Jinja is a good indicator to pause and think.)
Happy to talk more about that in a separate topic. If you think you’re at that point, I’ve started discussing and documenting those ideas in this GitHub issue (follow the links there, stsrting by that issue #14 I’ve cross-references other issues and pull requests there — if you’re not familiar with GitHub, feel free to ask me for direct links, I can write down a little tour of those issues / pull requests):
For further context, the initial idea was discussed here:
And I’ve mentioned that idea of keeping VM creation and configuration separate here:
I’ll keep following this thread either way, the Mullvad config interests me, so I won’t be far 