I find the solution, I can use the Dynaconf to load the config.yaml file, which will load the env variable name. And then read that variable using this name from .env file. I am not sure if there is any other approaches.

In normal case, it's not worthy. But as I mentioned in my question, for my case, the hierarchy of the config.yaml file provide me a flexible approach to instantiate the consumer for multiple topics.