I think your definitions don’t quite match common use. When people think about sideloading, they think about installing apps from a third-party source that are not approved by the primary vendor. That’s precisely what Google is going to block.

See the end of my pervious comment. The fact that we call that “sideloading” in common parlance is a magic trick Google has already played on us and we ate it up. Resist.

The way I understand sideloading is installing an app through a way that isn’t Play. So F-droid - as one example - is sideloading because you need to go through the overly dramatic warning messages to enable the install from unknown sources. If all the devs in F-droid’s repository theoretically registered with Google, nothing will change. The only difference is that Google wants to know who made it. They make it harder and shittier and thus limit our choices, yes. But they don’t block everything outright.

The problem arises for apps, whose developer doesn’t want Google and by legal extension the American judiciary to have access to their information. That’s a privacy concern that I find very concerning too. I’m not defending Google’s choices here. I hate it. I also don’t like the inevitable hyperbole going the other way.