I don't know if this will address what you're asking for or not, but you might consider creating a project template to use for when you need to create a new project with the same, basic types. I will give the caveat that I've tried to do this, but it wasn't successful.
Where I work we're trying to replace several small apps originally written in MS Access, with some WPF apps. However, our approach, which I don't recommend, has been write a general purpose WPF app that we have stored in TFS. Then when we need to create a new app, to replace one of those Access apps, we fork the main branch into another branch for the new app. (Note: we never merge the forked branch back to the main branch.) What this results in is lots of Visual Studio solutions that appear in the most recently used list, all named the same thing. Very confusing; the odds of opening the wrong solution are high. (Although the guy who came up with this idea is pleased as punch about his idea and he claims to have no problems with it. Meanwhile the rest of us have to suffer through.) What I have done, whenever I've had to start a new project based upon on main, basic project, is take a day to go through the code and rename the namespace in every place it appears. At least that way it will look different when I open VS.
This is the reason why I've considered trying to implement project templates. I think that the idea of project templates is sound. But so far the documentation on how to do this is sparse. I've not seen a course on Pluralsight nor LinkedIn Learning on Visual Studio project templates, so you're on your own.