They're good for teaching you why people often refactor the code that's generated... The problem is most scaffolds don't reflect a particular chief architects preferred style-guide, or software portfolio policy that has been adopted by company A, B or C. They can't read your mind. So, most have a generic structure that allows for refactoring easily enough by individuals or teams even if it is initially working backwards.
Better to have the option to use it than not I say... but if someone has a desired scaffold they want to use/reuse they should probably do the legwork then automate it so it's not wasted time each time.