I mean, I don't trust any companies who would keep and sell my data, especially if it's any sensitive data and/or they are supposed to aid to keep my privacy.

It is definitely not necessary for companies to keep my home address or phone number. If they tries to sell those data to third party companies, I would have second thoughts about buying from them.

You don't have to share the full logs. Just the lines for the previous few days (from when you're experiencing the problems) will do.

Electrum has a few advanced features that Bitcoin Core doesn't support. You can run a personal Electrum server which take information from your Bitcoin Core node.

Could you paste a copy of your debug.log, it would really be a huge help in terms of identifying the exact issue. Just use pastebin.com and send the link here.

Doubt it is real, to be honest. It would fetch much more value if its sold elsewhere in the darkweb presumably. It's fairly useful for hackers to obtain such information; scamming through social engineering, selling to advertisers etc. I bet it could fetch much more than the asking price here. It would be better to be wary of any social engineering attempts though.

Good on Trezor for scrubbing their user info regularly, hope to see other companies do the same.

Hmm. It could be a problem with how your wallet interacts with the node. Misbehaving node is likely a problem with your client rather than your ISP. It could also be that your banscore is too high and the node would just automatically reject the wallet. To clarify, which android wallet are you using?

You can try whitelisting your IP by putting whitelist=(IP ADDRESS), replacing IP address with the public IP address on your phone.
Electrum is probably the only effective one as most wallets are phasing out bloom filter at the moment and there isn't any defined standards yet.

My guess is that Comcast has been selectively blocking connections to try to conserve bandwidth for other users. Throttling is not uncommon for applications that are somewhat bandwidth intensive. That being said, could you share your debug.log? This would be able to confirm the theory.
The problem is not with your VPN. Starting with Bitcoin Core 0.19, bloom filter has been disabled by the client by default. In Bitcoin.conf, insert the following line: peerbloomfilters=1

Restart your client and try connecting again.

No. If your wallet is functioning correctly and there were transactions inside, the transactions would still be shown.

Are you certain that it is synchronized? Rescanning tends to take sometime as it has to scan through the blockchain for the transaction.

It's very unlikely that your GPUs were mining Bitcoin in the first place. GPUs are nowhere as fast as ASICs right now.

If you can check NiceHash, you should probably find that your GPUs are not mining Bitcoin but some other altcoins that has greater profitability as ASICs are not developed for that algorithm yet.

Nope. Addresses starting with 3 are P2SH (Pay to Script Hash) address. It allows the user to fulfill certain criteria before a transaction involving that address is valid. bc1 is a bech32 address, aka. native segwit. Address starting with 1 are P2PKH (Pay to Public Key Hash) address.

A multisig address has to be a P2SH address while a P2SH address doesn't necessarily has to be a multisig address.

The mining hashrate is not fully indicative of the price movement of Bitcoin. There appears to be some FUD about Bitcoin when the hashrate decreased after halving, presumably also because of the movement of a bunch of coins which were untouched over the years.

In the long term, I highly doubt that the hashrate would influence price significantly, especially given the fact that a temporary interruption wouldn't affect security at any level. The electrical interruption might be a factor in the decrease of hashrate but IMO, the halving was responsible for the bulk of the decrease in hashrate.

For your GPUs, are you using SHA256 or other algorithms?
Your estimated earnings based on 13.5TH hashrate is roughly 0.0001121BTC a day, subjected to the pool's fees, varience and as such. If your nicehash dashboard is showing 13.5TH, there is likely nothing wrong with your ASIC.

It isn't necessary to allow incoming and I doubt OP would fix his issue with this. As long as there are peers, OP's client should be functioning fine.

It certainly isn't normal to have your client getting new blocks so long after it starts getting propagated (propagation should only take several minutes at the worst case scenario). Have you done any hardware diagnostics? Your debug.log should provide some clues at least.

Bitcoin is not fiat though. It isn't a currency that is endorsed by the government. If anything, fiat is the resource that would be used during war. You probably won't see governments paying contractors in Bitcoin during a war. The spending during a war would take hundreds of billions and I highly doubt Bitcoin in its entirety would be able to finance even a significant portion of it.

Attacking Bitcoin through 51% would be a waste of resources and even if they manage to attack Bitcoin, it would quickly become worthless and all their resources would've gone to waste.

If you aren't getting any error when you dump the priv key, it would appear that there isn't an issue with the commands given.

To clarify, when you mean any address, you mean when you use any 2 different addresses from the same type? Ie, You're querying 2 different bc1 addresses, 2 different P2PWSH or 2 different legacy addresses? Does the address start with 5, K or L?

What good would it do if China hacks Bitcoin? Bitcoin doesn't belong to any country.

If you mean being able to hack Bitcoin by the use of 51% attacks, which is pretty much the only attack that they can execute, then you're wrong. In terms of the global transaction volume, Bitcoin isn't used by any government as a store of value. It would make sense if you could paralyse another country by restricting their financial flow but it can't be the case. The most that they can do is to stop the citizen from using Bitcoin which doesn't really affect people since most of the transactions are in fiat as of now.

Would've worked only if you are absolutely certain where all your coins are which is nearly always not the case.
Command prompt allows you to run Bitcoin Core with a specific flag. If you don't have a basic knowledge of using command prompt, I would encourage you to use this method instead, courtesy of achow101:
https://achow101.com/2016/07/Bitcoin-Core-Troubleshooting#option-startup

Add -upgradewallet to the string at the end.

If you do not already have a shortcut for Bitcoin Core, go to the start menu, right click on the Bitcoin Core program and select open file location. You should be able to see a shortcut for Bitcoin Core in that folder. Right click on its properties and in the target box, just add -upgradewallet to the end. After doing so once and seeing Bitcoin Core start up, you can do the same to remove the -upgradewallet flag from the shortcut.

What kind of business are you running? A brick and mortar store or an online website?

I don't encourage people who are running a business to use normal wallets or hardware wallets. It would be a lot more convenient for merchants to adopt POS services like Bitpay, cryptopayments etc. They streamline the process for you and you don't usually have to worry about menial stuff like this.
The network fee surges at times and it doesn't always cost so much to send funds. If possible, you should wait for a bit for the network to get less busy before sending the funds elsewhere. Sending the funds now would eat into your revenue by a significant portion.

They don't. A lot of the governments around the world do not disclose about the things that they invest in as it concerns national security. Let's treat crypto as a reserve currency. If governments disclose the amount of reserve that they have, it could have detrimental effects since outsiders would know exactly how much they have.

Governments like North Korea could potentially be using cryptos as a way to circumvent international sanctions and disclosing it would only make the world impose harsher sanctions.

Even if you do know the address, if it's an old backup, it would be better for you to resync the whole blockchain to ensure that you'll be able to get all the coins in the addresses within your wallet.dat.

Yes. Do keep a backup of your wallet.dat though (both your current and 2011). It's true that the wallet.dat files had its structured modified slightly but its not wholly incompatible. The client would be able to identify and upgrade your wallet.dat to ensure compatibility. Using cmd, navigate to the folder where you have your Bitcoin Core installed and start it with -upgradewallet flag.

Are you generating all 3 types of addresses? By default, Bitcoin Core only generates native segwit. Did you modify the conf file to generate legacy address?

How are you extracting the private key exactly? A single private key can be used to derive all 3 address types. Could you try dumping 2 different bc1 addresses and check the private keys?