Glad it was useful! It certainly is interesting work -- a lot to think about here ...
Agreed that did:web is very niche. I was discussing this with Rudy Fraser and he pointed out that there are shadow copies of the PLC directory (in fact rsky-relay currently uses its own copy), so if Bluesky PBC when away it could probably be rebuilt. So the current B-index has different implications in terms of the power of their administrative discussions and the impact of a financial collapse.
In terms of the what-ifs, I tend to look at things through a threat modeling lens. Sometimes threats can be prvented mitigated proactively; other times, it makes more sense to wait and do the mitigation and recovery afterwards.
I had seen the fedi hosting anlaysis when you did it (although it didn't click until now that you were the same person). Instance blocklists are another place where there's been concerns in fedi that relate to the B-index. A couple of years ago there were concerns that The Bad Space would somehow get used as a blocklist for the entire fediverse. These particular concerns were somewhat unrelaistic -- as I said at the time
"The Bad Space includes mastodon.social on its default blocklist – and mastodon.social is run by Mastodon gGmbH, who also maintains the Mastodon code base. Mastodon's not going to adopt a default blocklist that blocks mastodon.social, and Mastodon is currently over 80% of the fediverse. So The Bad Space isn't going to get adopted as a default by the entire fediverse."
But the underlying issue is real. One specific threat is that Meta has talked about providing moderation tools for fedi (out of the goodness of their hearts of course, nothing to worry about here) and it wouldn't surprise me if they embed their own blocklist as part of it, and maybe even over time make that a requirement for federating with threads.net.