So, I absolutely agree with regards to normal federated systems. Your examples are examples for a good reason.
But Bluesky works a bit differently. Users don't work as like, "user@domain", you have the moral equivalent of a UUID. If the host of your PDS decides to defederate with someone else's host, that doesn't mean you're prevented from getting their posts, it just means that like, it's a bit harder to. And if you don't like what your PDS's host chooses with regards to defederation, you move to a different one, and when you do, you retain your entire following/follower graph, and people who follow you don't necessarily even notice..
The closest way to think about it is git, IMHO. GitHub hosts a copy of your project (a PDS of your posts), and you can have one locally too. You can also put up copies elsewhere, and people can grab copies of your project elsewhere. If GitHub decides to stop hosting your project, you can put it up on another host, no problem. If GitHub decides to stop hosting a project you want to follow, you can follow where they move.
This is in sharp contrast to email or Mastodon, though in my understanding, Mastodon has made it a bit easier to move servers lately.
Most criticism of BlueSky/AT tends to be that it's too hard to do things like private accounts, keeping your block/mutelist private, or even deleting posts. (Though the latter is better now thanks to the addition of the moral equivalent of git rebase.)