Ah, ok.
What you want is have the animated banner "Wii Transfer tool" channel inside your nSwitch channel, both on sysNAND and Neek?
There are therefore two option :
1. use WTT as base, and replace the dol.
2. use Nswitch as base, and replace the banner.
Personally, I would go with the second option, as it already contains the proper channel's TitleID to properly exit back to sysNAND when exiting a game.
On Wii it'll look fine.
On WiiU the issue will be that you'll have 2 identical channels on your sysmenu (you can delete the real WTT from emuNAND and keep only the nswitch one), but on sysNAND I don't recommend deleting system channels.
The first option will (should) work but on vWii you'll replace the official system channel with a patched dol (which is what's the WUP installer does) (is that the correct name? replacing Mii channel's app with hackmii launcher)
On Wii that's fine, you'll just add a new channel on sysmenu.
What I understand you did:
The "neek" channel is actually a homebrew (Nswitch) which detects whether you already are in neek environment or not.
If you are on sysNAND, it reboots the console with patched kernel (neek).
if you are on neek, it reboots the console (going back to sysNAND).
What I understand is that you made a new wad, and installed it using USBLoaderGX's emuNAND manager. it means the channel is installed on your emuNAND, and not sysNAND.
If you installed the wad using USBGX only to get that channel installed and available when you are in neek environment, in order to "exit" neek, then that's good ! that's how you need to use that (exit neek) channel.
If you installed the wad using USBGX and try to launch it from USBGX interface in order to boot into neek, that's NOT where you should install it ! that channel should be installed on sysNAND, usbgx has the ability to list channels from sysNAND too and nswitch will detect sysNAND and rebot into neek.
if you launch the channel by listing emuNAND channels from USBGX, it'll only create issues.
because USBGX will first set the console in "emuNAND", then launch the channel (nswitch) and you'll be in "emuNAND" mode when nswitch checks if you are on sysNAND or not....if you are on emuNAND, it will detects and interpret that you already are on neek (while you are not) and will try to reboot the console to return to sysNAND.
I'm not sure this is the expected result.
If your network issue is from neek, then I don't know. it's strange that the banner animation would try to check internet (eve though it's possible, as Vote channel or weather channel did).
But what I remember is that the network had issues on Neek. some games (all?) network don't work on neek. I tried only "Uno" card game, but it never worked, even if the SYSCONF and network was from the same console/network/setup.
I guess if the banner checks if the network is init, it'll fail before launching the app.