Package managers that package package managers

Honest question: what are the implications of what’s revealed in the post?

I took away that two Package URLs can represent roughly the same thing (maybe there’s a need for a “is kind of” relationship) and I guess that paths in PATH needs to be protected from spurious edits (not because Nix can install apt on a Debian system does it mean that I want /usr/bin/apt to be the Nix provided one)

But I wonder if others are seeing other takeaways? My first reaction is that sometimes package managers are packaged in foreign ecosystems not because that’s how the package managers client is meant to be installed but to offer libraries for cross-system development. Does the fact that they’re package managers create a unique problem compared to crypto libraries or curl bindings?