I agree that it would be convenient for layers that rely on the same source to be able to coexist in an offline map, but I have a feeling we are not going to see that anytime soon.
You would have to create a view for every layer that you have control over, then add those views to the map instead, so each layer/table in your map would be pointed to a different service.
Not sure about the Join View Layers, but as you are discussing in your other reply, I do have a feeling that a script will be required to move data between services. The script could easily capture the layers that match, even if you have to truncate field names on your own end.
You could attempt to create a new layer from the join/view layer service as a template. You may also wish to create your own service as a link to the existing service, but I have a feeling you won't be able to necessarily trick it to sync that way. At some point, the editor fields and the globalid field are going to have to exist in your own service.
There are also ways to have collaborations where services can sync from one org to another, but that could be a security issue depending on your orgs (and I have only seen it function once, and I believe it had some hiccups - that was also on Enterprise and not AGOL.)
Where the data lives (AGOL or ArcGIS Enterprise) I am sure will also be important on whatever the final solution is here for you.
Hope this helps.
Mitchell Grafstein, Horticultural Inspector 1, NYS Dept. of Agriculture and Markets