That is correct. However, rather than expanding this swamp, I would support issuing additional /28s to these organizations and draining the early allocation swamp through attrition.
Correct, hence my suggestion that they simply be issued new /28s.
Note there are actually multiple blocks as pointed out. Forever is a very long time.
The better solution, which does not waste all of them forever, is to allocate new /28s to those organizations that need more than a /32 ask that they not make any new allocations or assignments within the original /32, and return the /32 when or if they ever vacate it through attrition.
For organizations that are lucky enough to have the correct neighbor vacate their /32, their prefix could, then, be expanded to a /28 without issue.
Even with this policy, most of that space will remain wasted anyway, it will just be wasted in a different place where it can never be used for a different purpose.
They do not, actually. While 30,064,771,072 sounds like a lot of /64s, the simple reality is that when you’re handing them out to end-users 65,536 at a time and to ISPs 4,294,967,296 at a time (minimum), it’s really not so many. When you consider that RIRs are given more than 1024 times that amount of space each time they apply to IANA and that no RIR has even come close to needing a second /12 from IANA so far, I think it is better to hold that particular space in reserve until its current mess is cleaned up through attrition, even if that never happens.