I promise this is my last post about this topic ...
As I see it, within my knowledge in operating systems, not in Android, but do not think it's very different, we have three problems in one. The small size of the RAM, the small size of the OneNAND (especially for those who have a slower MoviNAND) and increasing system size in KK . All this obvious.
By the system occupying more space, along with the applications that are loaded at startup , there will be instructions in the operating system that is used quite often that they're not always in RAM memory, and this has to slow down a lot by having to make frequent readings in the MoviNAND. What we most despair is the lack of fluidity to move through the system environment and in certain applications that use a lot of system resources. Given that the dalvik cache is housed in the MoviNAND and is where the apps are started, it makes little sense to have the apps (not dalvik) in the OneNAND.
So, what I think that expedite quite the environment operation would, spend all apps to moviNAND, keep dalvik also there, and if with this the space required to locate the system in the OneNAND is achieved, I think I'd win much in performance.
Of course, you have to cheat the system somehow so that RW application operations will continue running in the OneNAND datadata, with links or otherwise if this is possible.
I do not know if all that we have discussed will do any good or if it's too complex to carry out. You are the master.
Best Regards