If I get it right, you have not yet decided how you are going to implement the temporal aspect of your database. You could use an intrinsic way of the DBMS (eg triggers, logging, special mechanisms like Change Data Capture etc). But anyhow you would ensist on the relational model.
Therefore, the general answer would be that Entity Framework should have no problem playing with any relational model as long as there is a proper EF data provider for the specific DBMS.
However, regardless of your final decision on how you would implement the temporal aspect of the database, I would be really suspicious regarding performance and definetely build a load testing mechanism before making the transition.
Hope I helped!