Yes a new kind, but just for kind 1. Then make it a choice to use kind 1 or the new kind. Every other event type can be reused.
Discussion
I see. Not a perfect solution, but I suppose for the other event kinds, the Twitter-like clients could just hide all events with an a tag. I still think allowing users to whitelist communities that should be aggregated is a good idea. Implementing that wouldn’t conflict with anything, it would just be a client-side thing