I have tested this and it works well however I am having trouble implementing it with MAIO (moonshell all in one.) To use this properly we really need the R4s to autoboot to
moonshell on startup and then return to
moonshell on soft reset. If we have to run
moonshell from Wood first and then start a ROM from there then there really isn't much point in doing it.
The original R4 is easy. You just need to encrpt the moonshl2.nds and rename it to _DS_MENU.DAT then decrypt the original _DS_MENU.DAT and use it in extlink and resetmse.
The R4iGold and R4IDSN are a little trickier as they will not run moonshl2.nds from boot no matter what you do. The only way around this was to modify the _DS_MENU.DAT or _DSMENU.DAT files to use an alternative ini file set on boot and soft reset solely for the purpose of using Wood's autoboot feature to run Moonshl2.nds. We then just renamed an unmodified copy of the DAT file to WOODR4.NDS which is used by
moonshell extlink and favlauncher to launch ROMs via the normal autorun ini files which are cleared each time by iniclear.
Due to the way Wood now handles its own .ini files the alternate autoboot method for moonshl2.nds no longer works. I don't see the point in using the new extlink feature if I can't get moonshell2 to autoboot on startup and softreset back to moonshell. I haven't spent a long time on it but have so far not found a workaround.