I think the OP is referring to accessing the config 5 layers down from the controller. I've run into it myself. To be able to do that, you have to add Options<T> to the constructor of every class in the chain and then configure DI for it. It just has bad code smell.
On my last project, I just assigned the configs to a static class that's available everywhere and the code was just simply much cleaner.