Those options could all be turned off, right? In our code for instance there tends to be a ton of post-processing for imported files which means the optimizations would be additional overhead for us because we have to disable them again right away. Actually, we don’t even generate many materials in Blender, we just give them unique names and an identifiable color and then put in the proper material on the BJS side. For shader-based materials this is simply required, for instance.
Therefore, I second @sebavan’s comment that a special tool would perhaps do a better job. Maybe a general post-processing framework running as a node app where you can run all sorts of optimizations and put in your own callbacks using the Babylon API to swap materials etc.? Sorta like a SAX parser for Babylon files… I would use something like this in a heartbeat if it was available. That would allow people to do all the post-processing of babylon files during the build stage instead of at run/load time.
edit: Can you put shader code into babylon files?