Hello @RajeshR-0720 - Welcome to Q&A and thank you for posting here!
My two cents on the matter is that the configs that go into host.json
are global by design (irrespective of binding type) and used during the instantiation of the runtime, whereas something like defining distinct values for visibilityTimeout
property for each message is a more granular detail in scope & specific to an abstraction where the messages flow through the runtime itself. I'd assume that's mainly why this configuration was put together the way it is today and how its functionalities work presently.
Since your post is suggestive of expanding an existing feature rather than a how-to or a troubleshooting question, I invite you to engage the Functions team directly on Functions host repo. Normally, we would recommend submitting a new feature on Azure UserVoice platform but it is currently under review for an improved experience.