There are different views on the GPLv2. Most of the contributors / developers on GPLv2 just wanted you to share back your code, so most litigation in this space followed that approach. Even there, it was at times pretty cooperative.
The SFC has a MUCH more aggressive view. They have views around DRM / unlocks on hardware and much more that are very user rights focused, but pose complications to developers. In the past though, they really couldn't pursue these claims because despite lots of contributors to projects, many didn't support their approach and so wouldn't work with them to make copyright claims. To give you a sense of some developers views:
"lawyering has become a nasty festering disease, and the SFC [Software Freedom Conservancy] and Bradley Kuhn has been the Typhoid Mary spreading the disease." - Linus Torvalds (key player in the Linux kernel development).
They and the EFF created Affero GPLv3 and GPLv3 to try and solve for some of the issues they felt were important, but developers didn't really get on board.
The key is SFC can now sue folks making and distributing devices with OSS software WITHOUT any permission or input from the creators and copyright holders of the software, that is what is so huge. And this is particularly important because many authors and copyright holders have different views on these issues compared to the SFC.
We went though this once with GPLv3 already. SAMBA for example moved pretty aggressively to GPLv3. I'm not sure apple kept contributing to it or updating it in their software once that happened.
Sure, its easier to get standing to enforce GPL, but the legal requirements of abiding by GPL have not changed due to this decision. The only change is that GPL violations that were hard to pursue are now easier and people that have been violating GPL will be more likely to face consequences.
If this that GPL projects have lower adoption rates then that is because fewer people who would have violated the license will bow avoid it. Similarly, if fewer projects areadr available as under GPL, it is because they are adopting licenses that have fewer restrictions.
I don't personally see the advantage of having a more difficult to enforce license. Either your license accurately matches your intent in a court of law and should be enforced rigorously, or it doesn't match your intent and you should use a different license.
Selectively enforced licenses seems like selectively enforced laws: ripe for corruption.
edit: if not, maybe you're trying to say that the people who control the license to the project (and have the contributors' agreements to prove it) can't relicense the code however they want (and however is allowed in the agreement) for whoever they want? Because I don't think that's true.