Have you considered switching your ISP?
Because I think the latency issue isn't from ethermine because I'm getting 24ms and 20ms average latency for east and west US servers respectively and I'm even from Asia.

Use blockchair explorer (https://blockchair.com/bitcoin) to view the transactions and click the switch "USD-BTC" and the USD value should be the average value on that transaction's date, not based from the current price.
Then get the current USD value though other means.

There's no address in the blockchain, so base it from the timestamp of the block(s) where the transactions are included, and its script type if identifiable.

The wallet is the client, in your case: Bitcoin Core; the address is the easy-to-copy representation of the script to receive bitcoins, or simply it's the string that starts with '1', '3' or 'bc1'.
Yes, your wallet can create as many addresses as your machine can handle, you don't need to create a new wallet.dat.
The balance displayed is based from the total value of all of your UTXO, unspent transaction outputs (in other words: unspent received transactions),
those are in the blockchain, your wallet only contains the keys that enable you to spend them.

Lastly, currently there's no risk in keeping your old outputs but there's no harm on sending them to a new script type for future-proofing purposes, aside from the transaction fee.
The decision is yours.

I bet they will reply with something like: "your recovery phrase might be an outdated copy after you change your password".
Because the walletID and password that it's producing in the recovery page is wrong, you might have changed your password at some point and didn't made a backup of the new phrase.

With that, try to remember any new passwords that you might have set.

Rename your Armorylog.txt (where you got the logs in the first page) as a backup and launch Armory, after a few minutes, close it.
Then share the new logs from the newly created Armorylog.txt (automatically created after using Armory),
it'll take a ton of replies to get the actual issue but with the logs, users may be able to point out the current issue.

Normally, Electrum will detect it upon opening the wallet file.
But since it's the encrypted seed that may be affected, Electrum can't detect if it's corrupted.

Anyways, if you try the post above and it resulted with something like:
The seed may be corrupted.

Recovering a corrupted file is a job for data professionals and out of my scope, sry.

He mentioned most "old transactions are missing" in the quoted post of his and in the screenshot, the oldest is from January 2018.
The unconfirmed are obviously P2SH-SegWit.

This gives me an impression that your wallet file is corrupted because it seemed to have accepted that particular password but the seed that it should've displayed is missing.
(I can't reproduce unfortunately)

Also, a wallet without a seed (eg. imported) shouldn't have a clickable "seed" option, it'll be grayed-out.

How old are those "old transactions"? If those are older than 2017, I highly doubt that they're included in your (P2SH) SegWit Ledger wallet because SegWit wasn't available in Ledger before that date.
You might need to import your seed phrase into a legacy wallet for the older transactions to show up (in Electrum, select legacy when prompted for address type).

For the newer unconfirmed transactions, I second NeuroticFish's link.
If it didn't worked and you have a passphrase in Ledger, review my previous post's notes about the passphrase.

Unfortunately, the legit free accelerators don't accept transactions with very low fee rate, they have a minimum.
Best you can do to those 2 non-RBF txns is to wait and do not re-broadcast them though "fake accelerators" or "push" service so they will be dropped from mempools after a few (2+) weeks for you to be able to re-send them with higher fee.

It's hard to tell just by the wallet.dat's size but surely, the "900kB" wallet is from an old version since newer ones are preloaded with thousands of key pairs making the initial size at least 1.3-1.4MB.

But if those wallets were used before, they should at least have "unknown" transactions in the history once loaded.
Also, it's already 98% sync and there are no transactions found, that's not a good sign for the currently loaded wallet.dat.

If you finished syncing and there's no balance, try to rescan the blockchain after opening both wallets (File->Open Wallet).
The command is rescanblockchain (RPC command usage link), that process will be slow but not as slow as downloading the Blockchain.

The problem is most wallets don't support BIP38 encrypted private key, you'll need to decrypt the private into WIF first before importing them to any wallet,
you can use an offline version of bitaddress to decrypt it, paste the BIP38 private key in "Wallet Details->Enter Private Key", click "View Details";
Then a new line with "Enter BIP38 Passphrase" below will be displayed, type your password there and click "Decrypt BIP38".
After that, your 'WIF Private key' that can be imported to those wallet will be displayed below, copy 'compressed' or 'uncompressed' depending on the address that you've funded.

For the next query, there are no difference when it comes with paper wallet safety, be it 2013 or 2021,
it's still based on how you handle and the private key and how you generated it.

Have you ticked "BIP39 seed" in the 'options' under the seed? Yes?
If the addresses are different, you might have to include the passphrase like previously mentioned.

Note: it's not the password that you type at the last part of wallet creation.
To enable it: tick "Extend this seed with custom words" above BIP39 in the 'options' and you'll be able to input your passphrase in the next window.

I'm talking about this reply:


Then in Armory, set bitcoin's data directory that you've chosen by following the last sentence.
Same as the post above.

To be fair, the site doesn't calculate it base from the user's specs, it has default values and formula for 4+ prefix: /src/main.js#L49-L62
Prefix length: 1 = 1second | 2 = 1minute | 3 = 20minutes | 4 and above = 20*[58^(prefix length - 4)] hours.

But it is indeed a lot slower than VanitySearch or even old Vanitygen, it seems not optimized for newer hardware that it won't even use the full speed of each CPU cores.

The link provided by Husna is for Coinbase web or Coinbase App, and based from your reply, you're using the mentioned wallet.
In your previous reply, you've said "Coinbase Wallet".

Those are two different wallets but both owned by Coinbase, my previous reply is for "Coinbase Wallet", it wont work in "Coinbase" since they don't provide you a recovery phrase.

Your node is pruned just like HCP guessed:
Bitcoin core automatically set it on when it detected that the data directory cannot contain all the blocks and other files.
So first look for bitcoin-qt's prune settings in "Settings->Options...->Prune block storage to", if it was ticked, uncheck it.
Also, if you've created a bitcoin.conf file in bitcoin datadir, remove any entry for pruning and if you're running using a shortcut, check if you've added any pruning parameters.

Finally, after disabling it, you'll need to sync Bitcoin Core again from start.
But make sure that you have at least 4000GB of free space in that disk.

Those are already pre-generated in the wallet file, 1000 receiving and 1000 change addresses. They are not randomly generated, all are based from your "hdseed".
In the 'receive' tab, the first to be displayed is the first in the index, the next is the second, etc. etc.

If you really want to "see" them, you can use dumpwallet command (doc), but that includes sensitive data like the hdseed, extended private masterkey and the addresses' private keys.
So, only do this to a "for testing" wallet.

In the data dump (include a .txt extension if you want to open it directly with a txt editor),
look for the derivation paths like hdkeypath=m/0'/0'/0'.
The example should be the first address that displayed in the receive tab, hdkeypath=m/0'/0'/1' is the second and hdkeypath=m/0'/0'/2 3'is the third.
The change addresses' hdkeypath starts with hdkeypath=m/0'/1'/0' then hdkeypath=m/0'/1'/1' for the second, etc.

Lastly, the wallet will generate more keys to keep a 1000 unused keys per chain after you've used the first in the index.

The app doesn't support signing a message natively but you can import the "recovery phrase" you can get from the 'setting icon' to a wallet that supports BIP39 seed.
I'd suggest Electrum and sign a message using it, your Bitcoin address should appear first in the 'addresses' tab.

Here's a short tutorial:

• Get your Coinbase Wallet App's "recovery phrase" in the Settings (you need to type your pin), that's the 12-random-words, copy it to a piece of paper.
• Download Electrum [link] (Stand-Alone if Windows) and I'd recommend you to verify its signature [tutorial], then launch it.
• During wallet creation, select the options: "Standard wallet->I already have a seed->type the recovery phrase->Click 'Options'->tick 'BIP 39 seed'->Next."
• In the next window, select "legacy (p2pkh)" for address that starts with '1' or "native segwit (p2wpkh)" for address that starts with 'bc1', depending on what you need to sign.
• Finish creating the wallet, I'd recommend setting a strong password; once done, enable the addresses tab using "View->Show addresses", then click "Addresses".
• To sign a message: Use "Tools->Sign/verify message", type your message, paste your address and click "sign", the signature will appear, then format it using the guide in the OP.

BTW, messages signed with the SegWit address wont be valid for most clients, only Electrum and others (I don't know any other client),
you must include that as a note to whomever you're sending the message to.

Important note: Make sure not to paste the seed phrase to any text editor, online posts or email, that alone can control all of your funds (you can do the message signing offline).

That speed looks like Bitcoin core is syncing in the background instead of Armory 'preparing database'.

Is the path to Bitcoin's directory correctly set in Armory? The one you've set in HCP's reply "-choosedatadir".
Because if it's not set, Armory will launch bitcoind with the default bitcoin datadir and since the blockchain isn't there, it'll sync from scratch instead of using the already downloaded blockchain.
You can set it in "File->Settings->Bitcoin Home Directory" and restart Armory (close any lingering processes before launching Armory, or restart PC).

Which of the transaction to bc1qz6k55y7z20azt596u80mtp0p53v9qnrj534t3k is yours?
But since you've mentioned "mining address" and "cant be changed", I'd take yours is the one from this address: 1Jucx1ny7mpxWwTfqVt4LTNyT4NPeosDs6

My question: is that a vanity address? If yes, where/how did you create it?
Because there are a couple of online sites where you can create compromised vanity addresses.