Socket dependency on another socket

I have an issue where sometimes one socket becomes redundant when another socket is not defined in a specific configuration.

For example, if I have a socket that performs a Boolean operation with an object, I’ll need an additional socket to input the object’s name and perhaps other parameters. However, if I choose not to use the Boolean operation, I don’t actually need all the additional sockets. It would be helpful if there were a mechanism to disable or hide sockets based on the state of a specific socket or certain rules.

Below is a screenshot demonstrating this capability in the Solidify modifier I’ve highlighted in red what becomes disabled due to other settings that haven’t been defined. Additionally, I’ve marked in Cyan a dropdown list that also hides additional settings not currently visible in the screenshot.

For example, in the following screenshot, I’ve highlighted the option to hide the socket from the modifier. However, it’s not possible to activate a driver there that would link the action to the presence of another value.