I don't think using Entity Framework (EF) will be a good fit for this project you're working on. One of the main benefits of using EF is the object graph; it takes care of recognizing new records, updated records and so on.
If you are working with dynamic objects and tables where you truly only know where your underlying data store is at runtime, then I would opt for using a generic database class with parameterized stored procedures.
Obviously the Entity Framework has gotten incredibly popular, but, there's nothing wrong with executing SQL the ol' fashioned way. EF doesn't have to be the only way you interact with your database.