Why do people write boilerplates from the basics instead of forking an existing boilerplate and writing from above?

Question

open source

I looked through the stories of a couple dozen popular boilerplates (react, react-native, nodejs) and none of these raps were forked from the other.
1. Am I missing something fundamental here? Why do people write them from the basics instead of forking an existing boilerplate and writing from above?
2. Let's say I want to create my own boilerplate because the existing ones are not specialized enough for my company's needs. This boilerplate will be serviced almost exclusively by employees of my company. This boilerplate will remain open-source (probably under the MIT license). Do I have to reinvent the wheel by rewriting everything or can I fork the turnip and write from above? Are there any limitations/disadvantages with this approach?
3. I don't like the inscription "Forked from" when forking through the github ui. Usually this inscription means "forked, one and a half commits added and that's it", which in my case is not true. Can I do a `git clone`, change the address of the turnip and push it to my own turnip?
4. Maybe I can delete `.git` altogether, all references to the original authors and part of the code that I don't need and fill it all in my own turnip? Sounds pretty unfair, I must say. However, this action is not prohibited by anything, is it? I draw this conclusion based on the fact that this approach is proposed by most rap as the main way to start writing a project based on this boilerplate.

Answer 1

Because there is a fatal flaw .
PS In fact, react, react-native, nodejs, etc. differ from each other a little less than completely.

Answer 2

Maybe I can remove `.git` altogether, all references to the original authors and part of the code that I don't need and upload it all to my own turnip?

Technically you can. But must act in accordance with the license of the original.