Thanks for the correction on the memory side — 16 MB with a Z-buffer around 48 KB really does make RAM the wrong villain. Scanline triangles plus a cache-bound tight loop makes a lot more sense on a handheld. When the cache is the wall, have you been shrinking the working set (shorter strips, fewer live tris), or is it more about access order?
Viewing post in Building a Tiny 3D Renderer for a Tiny Handheld, Part 2 comments
Reducing unnecessary work is always the key. Also, as a solo dev making an original game, it's really important to keep the renderer code easy to understand and to iterate. I'm sure I'm close to feature complete, but I may still make some changes, so being able to make changes easily is as important as the code being fast.
Once I'm close to release I can then focus on extreme optimizations, even if they make the code a bit more complex to follow.