Unfortunately, I still didn't find a solution...
Encrypting a SQL database has its price. One of them is a larger memory footprint. On the one hand, because in addition to the encryption routines, these must also be linked and included in your program.
You can determine how much that is by looking at the size of a test project. First with an empty database unencrypted, and then the same project with the same empty but encrypted database. Then you will find the extra memory that you cannot avoid.
Then I wrote to you before that encrypting data simply leads to more memory consumption. At the time, I also advised you to only encrypt necessary information because encrypting public information takes up space, but contributes nothing to the security of public information.
You could test encryption with the internal library (J)B4XEncryption which may require less memory.