I don't think your opinion is "unpopular" but more making unfair assumptions about situations you imagine others to use it, while there is more situations a tool like this could be useful for.
Microsoft recognized this need by updating its .NET CLI to create projects based on project templates. I know for a fact that at least one FANG has a couple of internal tools to create projects and CICD infrastructure from scratch using project templates.
When I wrote my own framework, Nexus (for Nim), I wrote a CLI for this sort of thing. It uses variables in naming things, and is quite specialized. I don't think I could use a generic tool.
1. You have no clue about what "boilerplate" is required or why.
2. You know what's required but you need to generate the boilerplate often.
In the first case, just stop. Using a tool might give you some kind of result, but the quality of what you do is already subpar from the beginning. Learn your effing tools.
In the second case, stop, too. Work with a higher abstraction layer, instead.
> I know for a fact that at least one FANG has a couple of internal tools to create projects and CICD infrastructure from scratch using project templates.
Imagine what that means for the ICs in that FANG: They don't know why the boilerplate is what it is or what part they could or should replace with something more modern .