I am looking into purchasing the SEE SQLite Encryption Extension to replace the legacy CryptoAPI for encrypted password protected databases. I have a large amount of existing databases that I would potentially need to upgrade. Is SEE `sqlite3-see-cryptoapi.c` compatible with existing databases that are password protected using the legacy CryptoAPI? If so, is there any benefit to using this? Is it different/better than the legacy Password/CryptoAPI capabilities in SQLite pre-1.0.113.0? If not, could the encryption/password be removed using a pre-1.0.113.0 build and then encrypted using SEE afterwards?