This could be achieved within the UI and seems like a good idea.
Each kbin/lemmy instance decides to follow magazines/communities from others through activity pub and stores it locally for the instance.
Having the UI retrieve all local posts with the same magazine/community name (e.g. m/star_trek@kbin.social c/star_trek@lemmy.world). Wouldn't be hugely difficult, I believe Kbin uses postgres database as the local store. The community/instance should be columns you can search for, it would be a small SQL change.
Even if that wasn't an option, there is a means to get all of the magazines/communities from the kbin UI and retrieve all posts for a specific magazine/community. So you could do it entirely in a web client.
The combined view wouldn't change how you comment on specific posts. The issue is where do you post and what view would take dominance (e.g. if a magazine had themed itself).
The solution here would be to default to the local instance if it exists or the instance providing the most posts/comments. Perhaps with a drop downso users can choose.