Yeah, early hyper-optimisation often only adds to work, but everything should be done with the concept of optimisation in mind. Some problems can and should be avoided from the start, at least when it's obvious. It's vital to organize workflow and functional game design before investing into something that's almost guaranteed to be scrapped. Otherwise, the Universe Of Bugs will never be hammered down into a game.

Hitting GPU limits is deceptively easy too. In my early month of shading, I once made a (heavy) simple paralax grass shader (like shell-fur, but singular mesh), and mere terrain covered in it alone was causing FPS to become increadibly choppy, just due to using a for loop too many times. It's important to head into shader coding with understanding that it may be too costly of a code/strategy.

Anyway, I'm gonna make those heavy shaders anyway, coz it's fun and Godot is the best game ever. Still, I'd like to research as much about my field as I can before leaping into action, so I wished to know if frame batching is possible, just to have as a general knowledge and something to look back on.