I tried out DSiMenu++ briefly last week after I learned about TWLoader being discontinued. I have to admit, I was pretty confused by the whole affair. I'll be sticking to my AK2i for a while longer, but from what I remember:
- There didn't seem to be a way to make the ROM selection menu work just like a simple list, as it is on my AK2i. The Icon-based menu (mimicking the 3DS or DSi) seemed pretty unwieldy. This also applies to TWLoader, but DSiMenu++'s lower resolution exacerbated the issue for me.
- The release .zip (or was it .7z?) seemed to contain everything needed for all use-cases, but there didn't seem to be a clear, unambiguous, up-to-date ReadMe supplied within, dictating which sub-folders were needed in which cases. I struggled for a while on this - neither the OP for the DSiMenu++ thread nor the GitHub release page for the download I used seemed to lay this all out clearly. I wasn't comfortable reporting a documentation issue however, without being fully confident in what I thought should instead be said therein, i.e.without fully understanding it myself first.
- The documentation seemed to imply that it would be possible, when run "from" my 3DS, to run ROMs from my AK2i's SD card. However, when I tried copying the AK2i-related cards to my AK2i's SD card (replacing akmenu4.nds, I think was the filename), the AK2i became un-bootable (until I restored the original akmenu4.nds), and I seemed to get no additional options in DSiMenu++.
- It wasn't clear to me whether the project could, now or in the future, run DSi-Enhanced NDS titles in DSi-"mode" on the 3DS.
In all cases, perhaps there were options I'd missed, or they were "known" issues either with solutions in the works, or known workarounds had I researched further. Regardless, I'm thoroughly impressed with the development of nds-bootstrap, but I think I'll wait another couple of months before I try again with the front-ends.