It's generally better to just make a good password as opposed to doing something complicated like this. AES can be implemented in different ways as far as how it uses initialization vectors and salts, and how key stretching works. If you don't know what that means, don't worry, but the point is you'll have to encrypt with the same program, or a compatible one, or the result will be different. This might be a problem if you try to recover your wallet a few years down the line and can't find the program you used.
I'm pretty sure I will remember how the wallet containing all my funds is encrypted , I'll probably write it down too.
Also, although in this case the 20 character password may help to add entrophy to the 35 character password, it's generally bad practice to use "tricks" in an attempt to add entropy. For example if you hash 1234 with sha1(), although it may make guessing harder, it technically doesn't increase the entropy of the password. Encryption never adds entropy since it's deterministic. You only get the amount of entropy that you put in.
Yeah, it seems like I had not understood what entropy means.
But overall , would this improve the security , by making it harder to guess ?
I need the second password also because I'm going to try to create a paper version of the first one , just in case.
I would recommend that instead of doing that you just make one good password of at least 16 characters (longer if you use a non-random password or passphrase). Beyond 16 characters IMHO the increased risk of forgetting your password by far exceeds any additional security.
It is non random , so I was aiming for 25 - 50 characters. I was hoping 35 characters would be enough.