There are solutions to this problem and principally why core devs want to roll these out first ... before increasing the blocksize limit on the main tree.
I'll reply back on the thread that you're porting this from (when I get back there). Suffice to say that I believe that market forces can solve this (non)problem without centralized command and control from the Core devs.
As just one tangential observation, I note that my rather modest node seems to have encountered no issue in swallowing up the referenced block 364292.