Update: The best solution I found is to use Cycles instead to visualize the changes (if the material is compatible), because Cycles actually updates the changes immediately. And even If I have to wait a few secs for the render to clear up it's always way faster than waiting a whole minute everytime in EEVEE.
I'm also probably gonna make a feature request post about the following later, that is: when I go back to EEVEE, the shader has to recompile still because it doesn't do it in the background while in Cycles, so (if it was possible), adding an option to compile the EEVEE shader behind the curtains while in Cycles would be super time saving. Even if Cycles was a little slower while it background compiled, for complex shader nodes, not having to sit still waiting a min for that white loading shader to recompile every time I change a node is still much less tiring and much much faster. This would be a good workaround for everyone building complex EEVEE shaders who feels limited because of these wait times.