I would mostly agree with these ideas if only there wouldn't be one large obstacle in the face of having RSS publishing and consuming be considered "social media": the main tenet that makes social media, well "social", is the consumers' ability to interact with the content they're consuming. If the plan is missing that essential component, then it's not "social" media, it's perhaps a better way of consuming and aggregating media, but that's it.

If you want to bolt interactivity on top of RSS then my question is why use an XML document with a very limited vocabulary when you can have a JSON document with a wide (and extensible) vocabulary in the form of ActivityPub. (I don't mean to imply that the later is perfect, but it's a better fit than RSS). An ActivityPub actor's Outbox is exactly an RSS feed by a different name. Instead of a list of "content" items, it has a list of "interactions" the actor had with the rest of the ActivityPub ecosystem, but once you reach the interactions which signal new content, you get that RSS feed experience.