Have a class that holds all the interfaces
Of corse you could do that, but I think that it breaks some ideas of dependency injection:


You can see the dependencies of a class by looking of the constrcutor (in your case, that is not possible)
You can test classes by mock the dependencies passed to the contructor (in your case you have to mock more because the dependencies are not evident)
You decople dependencies by passing only what you need (also not given in your case)


Instead of creating some granular dependencies of needed objects, your proposal is to create lots of dependencies from a container object that provides a set of objects. I see also the risk, that such a container object tends to grow so it makes the life easier (but conflicts with the idea behind DI).