Content addressable IDs, or CIDs in IPFS are used to identity a document or object.
So the distinction here is objects (some record of data) vs entities (something that can take actions).
> The DID in this instance is the record of verifying who this entity is, and if they should be trusted to do that action.
I don't see why you wouldn't be able to use a CID for that. As long as the content the CID points to contains the record of the entity, and a cryptographic signature, you could do the exact same thing.
This doesn't mean that we cannot use content-addressing. For instance, in IPFS world, the DID could actually be using IPNS to point to a CID. This allows to have a persistent DID pointing to CIDs at different times. There's actually a DID method called IPID (based on IPFS), that uses a strategy similar to this.
Disclaimer: I'm working on a project[3] to create a content-addressable version of OWL2 (Web Ontology Language), so I'm certainly a bit biased.
[0]: https://arxiv.org/abs/1407.3561
[1]: https://medium.com/@ConsenSys/an-introduction-to-ipfs-9bba48...
[2]: https://en.wikipedia.org/wiki/Content-addressable_storage#Op...
While it doesn't have all the properties of DIDs, it has the most important ones, and comes with some other nice ones (automatic deduplication).