these same discussion we have over at the DVI forums. The issue on Satellite “links/FKs” depends on the DV loading. It is not possible to resolve links to satellites within a DV load effectivly. However this is only an issue for the *active* DV being loaded. Creating links to other external (meta/master/metrcis) DV/datastores are not affected by this limitation as long as you do not destroy source data in your sats. This means that for source data business keys are the dominant foreign keys in satellite. For metadata columns you can(and should) use surrogate keys.
IMO a good solution to these metadata issues is a hybrid “one (metadata) column to rule them all” approach. This resolves most these metadata referencing issues you are seeing.