Do you mean, just these parts of the single-sheet backup?:

Test Wallet

If so, then it's a useless backup, it contains nothing but the wallet ID and info in case you need to manually find it from your computer.

Last time I tried, importing the keys from the dumpwallet file worked for "importwallet" command.
Of course, not the actual wallet.dat file or the file from "backup wallet" option.

In OP's case, it's a file from dumpwallet command with '.dat' extension, looks like he accidentally added the '.dat' extension through this:

Isn't this the v0.3.19 that you're looking for: https://github.com/bitcoin/bitcoin/releases?after=v0.3.22rc1?
The page can still can continue down to v0.1.5 (https://github.com/bitcoin/bitcoin/releases?after=v0.1.6test1).

You have to compile it yourself.

How low is your Rig's RAM?
How much is the available memory (RAM) when you start Bitcoin Core?

If you're using dbcache in your config file or Qt settings, try to decrease it to half of your total RAM,
if it's already set to half, then lower it more.

---

The contents doesn't look like a wallet.dat to me, it's more of a "dumpwallet" command file export but OP might have included ".dat" extension to it.

If that's the case, then do a quick "back-read" of my previous replies because most were already answered and you seem to miss the most important parts.
I wont reply any more since I can assume that this will be easily solved based from the last paragraph of your post.

As an addition to the previous replies:
It will work even if command prompt wasn't launched as admin, but it wont be able to create an output file if the disk is protected.

Then read my previous replies for the reasons and solutions.

Now a different file in the chainstate folder is corrupted.

You can delete that particular file and restart but...
Check your HDD for hardware issues like bad sectors first so you wont lose more time on deleting corrupted files and trying over and over.
You can use HDDScan, Hard Disk Sentinel or other disk check-up tool online (most of them work with SSD too).

Now it's clearly the language barrier that's hampering this conversation since those are already explained in that quoted post.
Consider using a better translator like deepl.com/translator (if your language is supported) or post a new thread in your local board.

I'll just rephrase the important part from my post:
[1] You can specify the full path and [2] you can also just write "file.txt".
The difference is [1] will create the 'file.txt' to that 'path' while [2] will create the 'file.txt' where vanitysearch is located.

Lastly, checking "run this program as admin" in vanitysearch's properties wont run it as admin,
"command prompt" should be run as admin [right click start and select 'Command Prompt (Admin)'].

So, you're not going to spend it within that 5-8 years? If so, just create a "Paper Wallet" and keep it safe.
It's not something you can download or purchase,
basically, it's a private key and address from an offline generated wallet written on a piece of paper.

Worrying about that is unnecessary, you can always export the keys from famous wallets like Electrum and export it to other wallets.
Some BIP39 compliant wallets, Mycelium for example have a "seed phrase" that can be imported to other wallets.

You might need to know that Bitcoins aren't stored in the wallet, just the keys and it can be exported unless it's a "custodial wallet".

You didn't answered any of my questions... 
Either specifying the directory or not, will work, the difference is without the directory, the output file will be created in the directory where vanitysearch is.

Did you even try to run Vanitysearch as admin? Because if the disk is "protected" and without admin rights, any app wont be able to write files if it wasn't launched as admin.
I have tried it and it also didn't created an output file.

You can also specify the directory where there's no required elevated permission like your drives other than "C" for W10, that way you wont be needing admin privilege.
Lastly, you should put the prefix in the end of the command, Eg:

That question if for shlomogold since I've quoted his reply

As for the "Run as Admin", I have successfully reproduced his issue by pasting and running VanitySearch from the system disk which requires Admin rights (Windows10).
If I run it outside the system disk, it always produces an output file even without admin privileges.
That's why I'm asking about his OS and where vanitysearch's directory is.

What's your OS?
Is VanitySearch stored in a system disk or drive without elevated privileges?

If your OS is Windows, you need to start Command Prompt as administrator in order to create an output file.
If it was launched normally, it will just print the result and wont create an output file.

You can also consider the log's suggestion.

Add rpcworkqueue=64 to your data directory's bitcoin.conf file, create if your don't have one.
Or add it as a start parameter.

I believe it's the same as "Bitcoin Days Destroyed" which was explained here: https://bitcoin.stackexchange.com/questions/845/what-are-bitcoin-days-destroyed.
Maybe the reason why Blockchair is calling it "CoinDays" is because it's a multi-coin blockexplorer.

Contact TheQuin (https://bitcointalk.org/index.php?action=profile;u=143168) or post to their official thread here (https://bitcointalk.org/index.php?topic=320959.11300).
Most of the time, they will ask you to sign a message using the address where your deposit came from or the address in your 'Profile->Change Withdrawal Address'.

So be prepared and learn how to sign a message: tutorial: How to sign a message?!

Just a reminder to OP: Do not do anything to the data directory unless Bitcoin Core was properly shutdown.
I'll introduce more issues if you delete/rename those files while core is running.

As for the issue, the log says it all, you can follow jackg's reply delete/rename "060915.ldb" and it should work unless there's a hardware issue.

I mean the actual written steps.

He can use Electum to create the RAW TXs.
Broadcasting the low fee tx using Electrum and quickly (seconds-delay) broadcast the second to other blockexplorers will work
but that wont work for a well propagated unconfirmed non-RBF transaction, like if it was sent 1-5+ minutes ago.

The difference is, OP's transaction wasn't flagged as "replaceable", so he can't use that method.
IDK what his intention is but it looks like he's trying to find a workaround to something that requires a non-RBF transaction.

You can wipe your transaction history by using -zapwallettxes as an added start parameter or in the config file and clear your mempool by manually deleting 'mempool.dat'.
The order is: shutdown core - delete mempool - start with zapwallettxes.
But that wont stop your node from receiving your 1st transaction back to your mempool.

If you're fast enough, try to broadcast the new raw transaction in the console.
But again, it's up to your peers if they will accept the new conflicting non-RBF transaction (99% won't).

(Don't do this if your node is pruned)

Too bad, localbitcoins removed their blockexplorer's broadcast function.
I can't believe they accepted non-RBF double-spends and can successfully propagate it in 2015.

There seems to be an issue with python v2.7 when it comes with finding the correct directory?

Try to copy all of the contents of "btcrecover-master" into the root of python27 so both btcrecover and python use the same directory.
It should work.

BTW, I've tested a sample wallet with 1 lower-case letter typo and possible 2 missing numbers using the same setup:

My test:

wallet file: bananapeal12
Password: bananapeal12
token file: bananapeal-token.txt
Contents:

Command used: python btcrecover.py --wallet bananapeal12 --tokenlist bananapeal-tokens.txt --typos-replace %a --typos 2

Results:

And I said above, you need more than 8GB of RAM if you want to bruteforce higher than 2 typos with that password length.