Yes but not-quite-occasionally,
I've been plugging it once or twice a year to check the contents for possible corruption.

It worked at the end after updating 'Ledger Live' so it may not be the case.
He mentioned it in his last reply (the arrangement of his sentences is confusing):

You can check the "block height" where the transaction is included.
That way, you can get a close approximate of the txn's date based from the height even if blockexplorers' dates wont match;
In blockchain.com, it is labeled as "Included in Block".

Passcodes?

• BIP39 "Seed phrases" doesn't always consist of 12 words. It can be 3, 6, 9, 12, 15..... but not 10 since the entropy wont be a multiple of 32bits.
  
• "Passphrase" for Brainwallet can be 10-words since the input's number of words is irrelevant.
  
• Or are you thinking of a specific wallet/client with 10-words backup?

---

For questions like this, it's better to be posted on "Beginners & Help" board instead (link),
I'll also ask a mod to move this topic to that board.

The option is still available in version 0.96.5.
However, he used a new Armory installation and just imported the wallet/root-key so the wallet is already rescanned for balance and it ended up empty.

You can still try the latest version before throwing the towel, there could be an issue with v0.96.
As you can see in the note on 0.96's download page: www.bitcoinarmory.com (old Armory website), the latest release can now be downloaded from btcarmory.com.

Upgrade to the latest, then use "Help->Rebuild and Rescan Databases";
if still empty, try "Help->Rescan Balance" for the last time.

---

Nice observation
You can tell based from "390371 blocks", I see.

That's quite...
There's a limit on how many Bitcoins that will be generated which is very close to 21,000,0000, your balance was way beyond that.
Obviously, there's something wrong with that instance.

The actual latest version is v0.96.5 from btcarmory.com.
Anyways, since it synced, and the balance is 0, then the balance is actually not surprisingly zero.
You can try to install the latest version and rescan and rebuild Armory's database (it wont resyc Bitcoin core).

What happens if you use their "Device Change" link in their webpage?
It's only requiring email address, then some sort of "Voice Verification" as stated in their user manual: abbccoin.com/Aladdin_Pro_Wallet_Manual_English-v2.pdf (Pages 35-39)

Maybe it has something to do with the first or other logics of "Smart Timestamps":
github.com/bitcoin/bitcoin/blob/master/src/wallet/wallet.cpp#L2380-L2396

If not, it could be related to the "wrong timestamp" bug when using -rescan:
github.com/bitcoin/bitcoin/issues/6662

I see where this is coming from.
It's a matter of preference though, but I'd always suggest newbies not to use the advanced features such as hidden tabs or console.

Bitcoin has no custodian since it's a "decentralized digital currency" which is held by every nodes in the network.
No one is in full control of the blockchain.

If you like to contact the current developers, you can find them in Bitcoin's Repository: https://github.com/bitcoin/bitcoin/graphs/contributors

Honestly, this looks like has nothing to do with Bitcoin.
Specially the "Serial Number", a backup from bitcoin core wouldn't contain a serial number.
In fact, Bitcoin Client v0.1.0 doesn't even have an export/backup option, just manual copy-paste of the "wallet.dat" file.

Sadly, I can't add anything aside from my posts in the fist thread.

Just use the "Receive" tab.
From there, Electrum will automatically select one of your unused receiving address each time you create an invoice (receive queue).
That way, you don't have to manually check the addresses if those are already used, because as the consensus here: it's not recommended to reuse addresses.

Does btcrecover supports Samurai encrypted "auto backup"? (AFAIK it doesn't)

Anyway, for the token file: If you haven't changed "wirelessacedemic" and just changed the numbers and symbol, then it'll be easy.
You can use this simple token file:
The token file translated into: use "wirelessacademic" at the start, any 1~4 digits at the middle, and any symbol at the end.
This will get complicated if you've changed wirelessacademic into something else that you don't have any idea of, because it's long.

You can opt in for "Nested SegWit" addresses instead of "Native Segwit".
That way, you'll get the benefit of SegWit while keep using those services that doesn't support bech32 addresses.
The downside the total size of your transactions will be slightly higher than Native Segwit's but still lower than legacy (in vBytes).

You can make a Nested-SegWit Electrum wallet by manually generating a BIP39 seed and importing it to Electrum using the "Option" below the text box where you type the seed phrase,
and by selecting BIP39. You'll get an option to select "p2sh-segwit" in the next window.
If you decided to go for it, use a reputable BIP39 tool or use iancoleman's BIP39 tool (offline from source) to generate a BIP39 seed.

Try to generate more change addresses by typing this to the console (change "100" into higher value if you want to generate more):
"View->Show Console" to enable the console tab.

But it looks like there's more to this than being a 'change address issue'.

Blockchain.com and most wallets now only supports "WIF Private key" so if you're planning to use it, you must encode it first using the tools you've mentioned.
Take note of the security implications stated above.

Talking about safety, it's better if you can import the WIF PrvKey to an "Air-gap" PC instead since it looks like a lot of Bitcoins from 2014.
You can check the balance and spend from it using an online computer installed with the watch-only version of the offline wallet.
You can get the address from the restored wallet in the air-gap pc.
Electrum has such feature: https://bitcoinelectrum.com/how-to-spend-from-an-offline-paper-wallet-using-electrum/ | Electrum Website

You can also do the private key conversion in the air-gap PC where it's safe from hackers, viruses and malware.
Just download the source of bitaddress, other paper wallet tool or code, then transfer it to that PC.

Wikipedia: Air-Gap (networking)

I believe the statement "along with normal usage" indicates that it's based from a scenario when the flash drive is constantly being used to delete & copy files.
For cold storage purposes, the flash drive wont even be used so it wont "write" any more data so it should last longer than that.
For example, I have a dormant USB2.0 thumb drive from 9 years ago and the contents are still intact time I tried, guess it will be broken by the next year :D

Of course having multiple backup in different portable drives as a failsafe is recommended.

Seems like it, just a few minutes after you received the funds from CB, this transaction occurred: 587645349fb0e5ceb23498d4ae9862e3d157765539e14cb988fe626e8e868ae8
If you did not initiated that transfer, It's highly likely that your Electrum is compromised via a couple of factors or you're using a fake version.

Unfortunately, Bitcoin transactions are irreversible.
All you can do is to check the reason of the hack and learn from it.

Then it's good, you can import the funded address(es)' private keys to the other Armory wallet to spend its UTXOs together.
You already know how to export, yes?

Now, to be able to import keys in Armory, you have to be in "Advanced" or "Expert" mode (Menu: User->Advanced/Expert, then restart to switch),
Then you can now import individual keys to a wallet by double-clicking the wallet name and select: "Import/Sweep Private Keys".
Make sure to select "Import these addresses to your wallet" and not sweep, otherwise, it will immediately create a txn that'll spend its funds and send it to that wallet.

As far as Electrum and Bitcoin are concerned, that transaction is now confirmed (fully sent),
and any issues regarding the recipient not receiving the fund is out of the anyone's control since the transaction is now deep in the blockchain where it cannot be reversed.
All you can do is to contact the recipient.

You may also need to double-check the receiving address [3MU1CGBjnfg3FTt156ZramF9mnVCmjqAdN] if it matched with the one sent to you by the recipient.
All of the characters, not just the first and last few.