It was an intentional change in 3.2 to avoid the possibility of outdated instance cache data being saved and then erroneously relied on after that. The solution is to not explicitly populate before turning on caching, although of course it could create unnecessary repopulation if you had already populated the current settings just as a natural part of workflow. It's basically a safety feature to make sure the instance cache data is up to date when enabled. It may need to be looked at again, but consider my thoughts above and then let us know if you still don't like it.
- Oshyan
