What I have done is install the COTS software base in the template VM. I
generally choose /opt for COTS products to keep them separate.
Then I install a service to start the license manager in the one client
VM and create a desktop file pointing to that installed application
location. Install the desktop file in the template
/usr/share/applications but assign it in the start menu of just that one
VM. Look at qvm-service for how to assign the license manager service to
just that one VM instance.
Any VM may see the software on disk, but as long as you don't actually
run from the software template or other VMs then you should be good with
the license server seeing only the one install instance.
Things can get a bit trickier if the service/software demands to be able
to write to the system area of the template provided ro file system.
Then you may need some fixups performed prior to starting the license
service.
Other options might be to install in /usr/local in the client VM itself,
or even in your home directory if that is possible. The service is
likely required as before unless you write a script to launch the
license manager, wait for it, and then launch the application when the
license manager is ready.
My worst case situation would be a standalone VM, but I haven't found
anything quite that stubborn just yet.
Steve