Set up the profile defaults so when you create the profile, it points reasonably well to where you intend the other database to go.
I remember doing some things from outlines because you could similarly program the server / database to retrieve the proper information from there, and you wouldn't be redesigning on every deployment.
I know there are some ways to embed views that won't let you do the simple @function programming to specify them. And I've avoided them in my designs, because they don't handle loose coupling like what you're looking for.