I am not sure what you mean by *all the branching* for a new project.
To some extent, I can see where defining a standard set of folders within a branch would be helpful. Automating this might save some time.
In general, however, with respect to branches, once you set up the Main branch folder structure (and add the solution etc.) creating branches is fairly easy to do. When you branch Main to Dev, for example, all the folders under the Main branch
automatically get replicated under the Dev branch.
For release branches, our guidance suggests creating them when you have stabilized the code in the Main branch, have passed certain quality gates, and are ready to ship the next release. Creating release branches in advance would be counter productive.
Perhaps I am missing something.
VS ALM Ranger