This is where content addressable URIs shine. IPFS is still pretty rough around the edges to use, but it allows hosting and distributing assets on the web without them being tied to a central server operator.
We could create a protocol for requesting content-addressable URLs over HTTP, but it wouldn't help with the problem described either.
It's more like an API with multiple implementations.
(Even just JSON serialization differences will pop up. For example, PHP always likes to escape forward slashes.)