Very interesting question.
Although I never had to deal with this kind of situation, I would like to give it a go and think about it with you.
Assuming you have your "skeleton" of hubs
in your raw vault and every table is potentially becoming a satellite
, there are 2 approaches here I guess.
You could replace the system generated Load_Date of your satellite
for the initial load with the load_date from the source system.
However, I would also put the source systems Start_Date and End_Date into the satellite
as regular attributes. This because of the fact, that they really are attributes, and you only leveraging them to simplify your loading technique.
Downsides would be here that you need a slightly modified pattern to load your satellites
initially, and the real load date would be lost.
Another approach could be to use the regular satellite
loading pattern in the raw vault. Attributes will stay attributes, and load date will stay the load date.
On the way out : for example when loading your data mart
, you could use the source systems load date to determine your SCD type 2 records instead of the regular system generated load date.
Also you could create a Business Vault View to represent the information like you want, while staying true to the raw vault approach.
I hope this will help a little !