Useless and harmful advice to reconfigure given when saved package config cannot be read

I sometimes see the advice given here:
https://github.com/haskell/cabal/blob/a97e1f13bdb28a3f761d55845f14a9072bee17ca/Cabal/src/Distribution/Simple/Configure.hs#L156-L158
Running `cabal configure` as advised has never solved the problem, but instead on top destroyed my `cabal.project.local` (#8408). (Nothing but removing the build folder has helped me so far.)

I _never_ run `cabal configure` in production (just `cabal build` directly), so why should this help? Rather, if `cabal` encounters some corrupt saved configuration upon `cabal build` it should execute `cabal build` as if there were no saved configuration lying around.