Maybe you ought to talk to Linus about that and get the real answer. What you just said is nonsense and Linus, if you can get his attention, will be happy to set you straight.
In case you can't get his attention, the real story is that Linus understood that letting Tridge create a clone of BK was just asking for trouble. Imagine if there was a commercial clone of git, done by people without access to the git source code. And it was used to read and write git repos. Now imagine that the commercial guys didn't really understand git and they made a mistake and that mistake corrupted part of the repo. And imagine that that corruption got picked up and propogated by the real git.
Kind of a mess, right? Especially when you consider that git is a distributed system. Actually happened to the Linux kernel when it was in BK because someone went and editted the metadata directly to "fix" a problem. How do you fix a problem that is in thousands of repos? We fixed it by putting knowledge of the Linux kernel and that problem into BK and doing a new release.
Linus was smart enough to realize that that sort of problem was extremely likely if people started using a Tridge created BK clone. And he realized that there was zero chance that when problems occurred that people would blame them on Tridge, BK would catch all the flack. So he got off BK because he was actually grateful for the help we provided and wasn't interested in causing us harm.
This was after him spending months arguing with Tridge that Tridge was doing the wrong thing.
But don't take my word for it, go ask him.