I don't think it's insurmountable, but they definitely have their work cut out for them.
Parent is suggesting that what you think is "recent code" isn't recent at all (if you mean the tech previews). The leaked internal builds are more recent, but only relatively so.Therefore you can't extrapolate the number of current bugs remaining from tech previews.
It's also possible that this whole thing is a psyops campaign and Microsoft has been sending out purposely buggy releases while sitting on a build that works amazingly so that they can appear to have released an excellent product under a major time crunch. Unlikely, but fun to think about.
I disagree on that part - I do not think that is reasonable. If I read correctly, your assumption is that pipeline for everything is: Develop > Test internally > polish > public testing > fix.
It's also reasonable to assume that not everything needs to be tested by the public, and only those deemed to require public testing were included in public previews.
There a lot of reasons to release 'old' code, especially on a large codebase. It's not that they intentionally send out "buggy releases while sitting on a build that works", but gating is complicated business.