Yes, non-persistent theme shuffle along with GBA VC (and previously TWLoader) screen bug are the negative effects of having the wrong cluster size. The brown line on TWiLight Menu++ doesn't happen anymore when nds-bootstrap v0.9.0-RC1 was introduced, although I did manage to clip the bottom edge on the lower screen this one time launching firmware.nds (CRC32: 836C9C90, 508 KB).Wasn't there a big problem with certain custom themes not working correctly due to the slowness of big cards? I didn't follow that too closely.
Theme shuffling was not likely to work when the wrong cluster size was used, yet miraculously start working again when you switched from (32 KB ⇄ 64 KB), even when it was the same 10 themes that were picked! This bug was seen on older versions of Anemone3DS (before v2.0.0), so no word if this holds true on latest v2.1.0. I haven't touched that theme manager in months because of a previous bad habit trying to horde all the themes on theme plaza. lol.
The idea of multiple storage partitions would work in a similar fashion as having EmuNAND(s) along with the same drawback of keeping track and referring to which one.I guess this has all been thoroughly investigated by now? I might have speculated that the 3DS could be persuaded to skip a partition by using the "hidden" and/or "active" flags.
- "Oh yes, my Pokemanz Ultra Moon in partition X is perfectly fine. Tee hee, I mean my other copy on partition Z is the one giving me trouble."
***
The only reasonable argument one could try to make is that this is like having two or more Nintendo 3DS folders without the above problems of having 'wrong cluster size'.
- Example: Split a 512 GB card into four 128 GB partitions. Your one massive card now acts like a four smaller separate but still big cards.