Could remotes and projects be treated similarly? They have their own containers, images, profiles. So why not treat them the same, as much as possible? Why not add a project as a remote, and then use the {remote}: notation to reference that project’s containers, profiles and images?
The following made me think that they are really very similar:
Unlike remotes, projects only apply to a limited set of objects with the exact set depending on the project configuration so it could get pretty confusing.
It also would also increase the logic in the client as we’d need to figure out whether you’re dealing with two remotes that are just different projects on the same server or if you’re dealing with two different servers as the feature set and APIs when doing cross-project operations is not at all the same as when doing cross-server.