I'm sure that will be very useful for beginners, I know it would have helped me when I started out.
Hyperspin is SO CONFUSING when you're new and it's not helped by the lack of good tutorials. To me it would make it much easier for newcomers if they merged programs together. They should bring HyperHQ, HyperlaunchHQ, module updater, Hyperspin etc together into a single package. THEN they could make it very easy to set up and use, with less confusion.
Until that happens though, a 'template' standard configuration would be great.
The separate programs and trying to get everything setup and working for the first time was overwhelming... My biggest issue wasn't the lack of guides so much as the fact that whenever I searched for something I'd find way more outdated and no longer correct information (for older versions) that it was hard to determine if the guide I was looking at was even relevant. Honestly a big help would be if they made separate sub-forums on the HS website for each major release so that you can simply search within the proper sub forum for the version you're running and know that the information is the RIGHT information.
In any case... once I figured everything out it's actually really easy to use. I can get a whole new system up and running within minutes now.
I also used to think that it would make more sense to merge HyperSpin HyperLaunch and HyperSync but honestly it doesn't make sense to merge them. I have one system setup that doesn't use HL at all, just HS and I'd rather not lug around HL if I didn't have to. Not to mention you can also use HL with a different front end if you'd prefer not use HyperSpin. As for HyperSync, once you get into the fringe of the artwork available out there, or if you start customizing your art HyperSync becomes a whole lot less useful and in a lot of cases you DONT want to run it as it might stomp over the way you've got things setup. It's better that it's its own app so that you can more directly control when it's run and how it's run.
Honestly there are 2 things I'd love to have integrated between HS and HL that isn't there... the system names. when I add a new system to HS I'd like the system name field to act like a combo-box where I can either type what I want, or drop down select from the official names within HL... a lot of times I have to load up HL and find the module and get the system name so that I can make sure I've set it up exactly how it expects... the other thing is HL knows which systems I've setup in HS... the least it could do is default the rom folder location to whatever I used in HS... let me change it if I want to but there's no good reason I should have to specify it twice.