Is there an elegant way of using CubeMX to generate code for two very different configurations in the same program?

Seems to exceed the scope of the tool.

Would really need a template, would see if any of the examples demonstrate multi-mode operation, but in most cases are overly simplistic and not real-world applications.

Thank for your answer. I was thinking about methods like having two MX projects, and making a copy-paste operation on one of the two projects to bring the second configuration in the main project and edit the files to change main() for a new function name that can be called. This may be automated with scripting. Just thinking loud.

ST: Your competitors' configuration tools explicitly provide for setting up multiple clock and power configurations so you can switch between them. This is important; lots of customers have this requirement (slow-lowpower <-> fast-highpower)!

"This may be automated with scripting."

Is it worth spending time on writing scripts to automate the automation (code generation)? That time can be spent on writing actual C code, which can also be much more configurable and modular than automatically generated buggy unstable and inflexible bloatware.

Thank you all for your answers! Until ST add this feature to the CubeMX, I will program the configuration changes directly. This is the simplest!