So to install all those patched IOSs you downloaded you need to install a patched IOS first (that is IOS236) according to a standard modmii auto-generated guide. Now only for simplicity am I going to boldy suggest you deviate from those normal steps (which btw if you had only used ModMii from the start u wouldn't be in this mess).
You can install an official unmodified/unpatched wad using any of the normal/official non-stubbed IOSs you already have installed as long as whatever your installing's version number isn't lower than what's currently installed. Also, I see that you already have IOS80 installed (unpatched but also unstubbed). So, I would suggest you install the 4.3U system menu IOS using any wad manager (mmm, yawmm, dopmii, whatever) - it is safe only because you have IOS80 already installed. You can try using dopmii if you want to try to retain your priiloader installation as others mentioned earlier but Ive never bothered with that before personally. That being said, after you install the 4.3U system menu, and you return to the homebrew channel, I would suggest you reinstall priiloader immediately before exiting the homebrew channel (if things go sour you might not easily get another chance).
I'm assuming you followed my earlier advice about making a second nand backup already, if not, do that first just in case.
So to reiterate, I suggest you make another nand backup, load up your sd card with a wad manager, 4.3U system menu wad, and priiloader installer, then launch the homebrew channel and install the 4.3U system menu wad, then immediately before exiting the HBC reinstall priiloader (assuming you didn't go out of your way to retain it in the previous step).
That should solve your issue. Then, use Modmii's main wizard function to mod your wii as if you were doing it for the first time (I. E. That it's a virgin) in order to properly mod your wii this time.
Main risk with this is losing power during the system menu installation (which is generally always a standard risk everyone faces unless u have a wii with bootmii installed as boot2) , barring that I am confident this should solve your problem but feel free to wait for someone else to agree that my plan is sound.