Unlocking an "EXTERNAL" Storage APFS, that was attached to a FAILED "INTERNAL" FileVault macOS, During Migration, where the recovery key, nor Mac login password doesn't work?

There were many community questions I would have loved to respond to, ironically, they get "locked out" after so long, I would change that feature. Within bounds of Questions for the community rule , "clear explanation of the issue", with all due respect, this would be my best description of the problem… Role out an updated operating system, and provide the choice of tying a FileVault recovery key with-or-without your AppleID, when FileVault is designed with it… The Customer adds the recovery key to an external device text file… without the AppleID… Why didn't the Developers and Engineers have a better answers other than "Unless either your login password works or the recovery process works, unfortunately your data is lost. Best of luck in recovering your data!! "???? What Customer Churn Percentile will it take to work the problem, and do it right? How well are we supporting our Developers and Engineers? How can we create a product that is so solid, so strong and REASONABLY affordable, our customers will WANT to buy a newer product sooner rather than later, eliminating never???

[Re-Titled By Moderator]