Nope. This is no defense of NQ's decision, but I don't think it's about performance and load time. The issue is with data storage in the cloud and how NQ isn't earning enough revenue to cover the costs of the game. Every construct you own has information about it that they need to maintain somewhere. Reducing the number of player-owned constructs means a cap on the size of the databases - that, they can future plan for. Static, dynamic, or space makes no difference - they exist, and they cost NQ money. Seems like this would be something to plan for in the very beginning. They should have decided how much data per player is sustainable and enacted limits. Doing it this late in the game means someone's estimate was waaay off, they've lost the minimum critical mass of subs to cover costs, or costs have risen so much since initial planning (they've been at it for like a decade) that the current format is unsustainable.
TL;DR - doesn't matter the type of core, NQ needs you to have less of them to save money