Image texture drivers

My puny lazy artist brain loves shader graphs, in all programs, especially blender's.

Recently I've been finding frustration over how few shader node values can be driver by other parent level nodes.

Quite often, our most complicated image based texture shaders are involving voronoi based tiling fixes. In these case we have a double up of textures, which can be frustrating to replace these textures if trying to build out more materials or adding even more instructions to the shader.

Chances are the artist will have even more texture based blending options, whether or notblending between mutliple different surfaces in the same material node.

The more complex the graph the more intense the tedium becomes to update, tweak or look dev these materials.

My suggestion is to open out the file path field of image texture nodes to accept a driver from another image texture node.

This would allow us to be able to look dev much more effectively and have much more felxibility with our shaders.

I'm personally also a big supporter of just having nested materials ala unreal engine material layers.

But overall having texture drivers as the parents for all of our textures in our graphs will breakout and reduce the mechanical overhead of building out complex texture libraries.

Hope you like my idea, hope it was somewhat concise and understandable, and I hope if you see use in this function you drop a upvote, cheers and thank you for your time!

p.s.

I said drivers, but any form of input would suffice, datablocks or just inputs for links