>4.x Sysnand
check
>sysNAND and not emuNAND before loading CN from the GW cart
Before you even have a Emunand formatted doesn't it boot directly into Sysnand, using the Browser exploit?
Yeah. And using GW 2.x is important because 3.x includes FIRM where the needed exploits are patched. Not only that, but the FIRM version needs to be one compatible with PastaCFW too (which is limited to FIRM from 4.1-4.5, 8.x and 9.x)
The following combinations might work:
GW 2.0-2.2 (any of them) with 4.x sysNAND
GW 2.3 with emuNAND 8.1
GW 2.4-2.6 (any of them) with emuNAND 9.2
Any higher version won't work (exploits are patched in GW's FIRM). For that reason, sysNAND higher than 4.x won't work (since higher firmware support wasn't added until 3.0)
I would try GW 2.0-2.2, but start with 2.2. Seems logical that running it on sysNAND has the highest chance of working.
Don't use any lower version than 2.0 final though. 2.0b1 and 2.0b2 had the 3DS bricking bug. Any lower version simply won't work because they're missing MultiROM support.
It might actually not matter which emuNAND version you use, as long as it's one compatible with those GW versions. PastaCFW isn't going to be using the emuNAND anyway. This is uncharted territory so other combinations than what I suggested might work, or maybe nothing works at all.