You should be fine with the first backup. You only need the private key to spend the coin. However, if the wallet.dat is anything like Bitcoin's, after you use 100 addresses, you need to backup again because it will generate another 100 addresses for the keypool. If you don't backup, you could lose those coins since the keys are generated randomly not deterministically.
Based on my observation, Bitcoin Core pregenerated 100 address everytime you key in the password or do anything with the wallet thus ensuring that the mempool stays at 100 addresses at all times. HD wallet solves this problem.You should be fine with the first backup. You only need the private key to spend the coin. However, if the wallet.dat is anything like Bitcoin's, after you use 100 addresses, you need to backup again because it will generate another 100 addresses for the keypool. If you don't backup, you could lose those coins since the keys are generated randomly not deterministically.
You touched on a question I had for a while now... at least one I was about ask..Q1) How do you know how many keys are left in your pool?
Q2) How do you see the keys in your pool (dumpwallet?)
Q2 I doubt there is anyway to see the pregenerated address. The only thing you can do is to see those already generated even if there is no TX by entering listreceivedbyaddress 0 true.
I just checked the Doge Core wallet and it showed my key pool size so i see i am good to go with the Doge wallet. I also checked some other qt's i have and there is no option
for it so i am guess with those type of wallets i don't have too backup every 100 addresses used?
a lot
