Sounds like a cool idea.
For the different wrappers, it would be nice to be able to select different versions via a drop-down. This would help with testing / troubleshooting.
Easy way to set that up would be to have a folder for the wrapper, and then sub-folders for each version.
The program then reads the sub-folders which could be simply named with a version number or you could have a config file in the top folder for the wrapper that specified the folders and version numbers.
You would also want to be able to have a program list with different available configs for each program you are wanting to run via this launcher. This should all be done through a config file or through multiple config files with a master config file that holds the filenames of each program's config file(s).
You can launch the programs by either creating batch files or Windows shortcuts. When setting up a new program, it would be good for the user to be able to select what to use.
This program is probably going to be easiest to make with Visual Basic or AutoIT Script.
Would be a great learning experience.
Please post code on GitHub and post the link here if you do decide to do this.
Edit: No matter what you use, you will have to be aware of and test different OS versions as the API has changed a bit over the years.
Some VB6 code has to be re-factored to work in newer OSes as does some stuff with AutoIT Script.
You can always do OS version tests and take a different code path for different OS versions.