Any chance you have a firewall, modem or ISP that's blocking connections?

That's normal, especially when you're low on RAM. I counted several TB read/writes in total just to sync Bitcoin Core with 8 GB RAM.

Importing a private key means just that: adding a private key to the wallet. That's it. No coins are moved, nothing gets "assigned" and nothing gets randomized.

I actually did that with 9375 potential private keys. It's quite demanding on system resources.

Since you can post, you're not proxybanned. None of that matters to your account anymore.

What "doesn't work"? I'd say it should be possible to run an old version of Electrum, if needed with your own node running an equally old version. Even if it can't sync all current blocks, you should be able to send your funds to a new Legacy address.

I've seen this so many times.... How can so many people lose access to the single most important thing when holding Bitcoin?

Has this worked before, back in the days when you were using this hardware wallet? Or did you always use Ledger's own software?

Did you find a solution? If so: please post it for others to read in the future.

You could use words instead of a password, to prevent mistakes writing it down. I prefer to use different seeds though, it seems easier.

This brings me to the next problem: the seed phrase is a human readable interpretation of a long random number. It's easy to write down, without a high risk of making mistakes.
Your password doesn't have that luxory. If you make a mistake, you're screwed.

Why? Writing down multiple seeds is a small effort to keep your funds safe.

I wouldn't do this. It's probably possible, but too many things can go wrong. For starters: what device are you going to use to create "child" seeds from your "parent" seed? How are you going to keep that safe? How are you going to verify you can still reproduce the same "child" seeds? How are you going to remember which "child" seeds you used for which (exotic) wallet?

That means you'll enter your seed on multiple devices, which (by definition) increases the risk of exposing your seed.

Amateur

Are you for real? I can already tell you your remaining balance: 0.

If it's only 5000 private keys, just import them into Bitcoin Core. It's the easiest way to check them privately.

95 for me please

Yes. Any transaction that includes an input that doesn't exist on another chain, can't be replayed elsewhere.

That should be okay if there other Forks have moved already. And that's usually the order in which I move Forkcoins.

Bestchange may show more options (all of them require the same caution).

Yes.

The BCH chain is a lot smaller than Bitcoin.

Here, that would be tax fraud. If you hide your money from taxes, you're on your own when caught.

I can't take a site filled with ads and links to their own site seriously. When I search for this, all I find is dozens of other crypto related sites posting the same "news".
Here's an opposing article: Let's Debunk Claims That the EU is Banning Anonymous Crypto Transactions or Self-Custodial Wallets. After skimming through, I'm not worried.

Step 1 before upgrading Bitcoin Core should be to make another backup of your wallet.dat, for instance on a new USB stick. Step 2 should be to create another backup on another stick.
Then you can start upgrading

What if you make a fat finger mistake, and lock your funds for 105 years? I can't find back the link, but it has happened to someone who found out the hard way that messing with timelocks has risks. All that's left is passing it on to his grandchildren who will have to do the same.

Your exchange, your bank, your Lambo dealer, your tax agency.... The list of potential questions is quite long.
Al Capone got caught on tax fraud. I don't want my money to be "off the books".

Real credit goes to djuragan I had to search hard to find back the link.

Why don't you put your money where your mouth is, follow the link you quoted, and share maybe 200 or so good posts that haven't been merited yet? I'll make you a deal: if I agree they're good (and I should be able to read them), I'll Merit them. If it's 200 good posts, I'll happily share 800 Merit with them. Good luck.

Shitposters complaining about Merit. All it proves is the system works as intended

If you have to ask, you probably shouldn't do this.

Things to think about:
Daily transactions mean daily transaction fees. 40x365=14600. To create that many transactions, you'll need that many different inputs. Or you need to build a long chain of transactions starting from the first one, spending your own change again.
You have no idea what fee you'll need 20 years from now. You may be overspending, or it could be too low to be able to  broadcast the transaction.
What if 20 years from now the Bitcoin protocol needs an update? Let's say you get 5 years to transfer all coins to a new quantum resistant encryption. Or the block time changes which changes your time lock?
I'll suggest what I've suggested before: it may be better to bury your private keys. If they're 20 meters under ground and it takes you 2 weeks to get there, you won't be spending it without thinking about it.
Or just work on your self control. Proper offline cold storage with offline signing is a lot more work than a hardware wallet.
What if a Fork happens in the future, and you can't sign a compatible transaction anymore?

I don't follow much Fork news, so I'm not sure if anything changed, but the lack of replay protection may be a problem for BCH/BSV/eCash. The sure solution is to include Fork dust on only that chain in your transaction.
I don't have a working BSV wallet, for the other 2 I can send you Fork dust. I do however have 2 BSV dust private keys, but the wallets are very shitty so sending it is annoying.

It went up:
BCH: $45k
BSV: $8k
eCash: $5k
BTG: $4k
BCD: $100

BCH and BTG can be stored on Ledger. BSV is the worst to deal with, and selling them is a hassle too. Not many exchanges except them, and the few that accept them shouldn't be trusted with much. So send small chunks only to reduce your risk.

Have you read my post on send-to-pubkey?
Using the full node and downloading the full chain is probably the easiest solution. Take it offline before entering your private key, create the transaction, and wipe it before ever going online again. It may be tiny compared to the Bitcoins you sold, but still no need risking your money in a hot wallet.

They changed the address format, but the old ones are still compatible. It's mainly meant to prevent wrong-chain deposits.

Not really: the OS should kill the program that runs out of memory instead of crashing.