You agree with rijndael because you think there's a disagreement. I don't disagree with what they said. What they described is how it is used.

Which I simply say is exactly the problem with BIP-39

Which is irrelevant to the fact that BIP-39 encoding doesn't include the derivation paths which makes it a half assed piece of patch work.

BIP 39 itself under motivation says:

"This seed can be later used to generate deterministic wallets using BIP-0032 or similar methods."

But it can't be used to generate a BIP-0032 wallet, because of all the missing information, hence the wallets recovery site, hence BIP-39 is a half assed piece of patch work.

Patch work, as in an amalgamation of incomplete parts.

and was nacked to the point of earning this label: "Comments-Summary: Unanimously Discourage for implementation"

Go on, go to the BIP, hit ctrl + f and paste the quote. https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki

Which has caused panic and confusion for people switching between wallets, or using a wallet that updated to use a different derivation path.

I don't think it matters what the intent is, I believe the function of "enhancing the management of wallet structures and derivation paths" will result in seed phrases getting naturally replaced. You already don't have a seed phrase for your lightning backup by the way. Liana wallet seems to assume that instead of backups, you'll just have so many devices with varying levels of accessibility to recover funds. If we decide to implement CTV or other covenants I don't think you'll be able to recover those wallets with BIP-39 either.

Half assed patchwork is workable for most people right now, but the world is changing brother! Get ready for it.