PROBLEM SOLVED
First, I installed a Homebrew Launcher Channel (since I didn't have one and am pretty sure I'd need it for the next step)
Second, I deleted 50_hbl_installer.rpx in sd:\wiiu\environments\tiramisu\modules\setup\50_hbl_installer.rpx (as Donnie-Burger directed)
PROBLEM SOLVED
The help is appreciated.
You basically could technically just remove the 50_hbl_installer file, but you would not have any (EASY) way to boot homebrew launcher without installing it as a channel if you remove hbl_installer. Forwarders would still work as they are basically one-off homebrew launcher that just point into specific homebrew (Unless they are whole homebrew program packaged into the title instead of being forwarders).
I have Homebrew launcher on both vWii and Wii U menu page, do I still need to do anything if I just delete the "...50_hbl_installer.rpx" file?
Sorry, I'm a noob.
using: Tiramisu Environment
No. If you have homebrew launcher as a wii u app/forwarder that works/worked before tiramisu, deleting the file is fine. Homebrew Launcher channel will work as it does, as will also forwarders and such. Wii menu's homebrew channel is not linked to Wii U's at all, your Wii and Wii U are essentially "two different consoles in one" - in sense. I am over simplifying this because there is things like Wii U homebrew to boot into Wii menu, and nintendo's official methods of booting Wii mode with Wii U features like gamepad play and so on and SO ON. But; your homebrew channel in wii mode is wii mode thing, it should stay it should work no matter what you do on Wii U side except brick the console.
My over simplified explanation about the 50_HBL_INSTALLER file is that it is essentially older style system patch, which makes homebrew launcher run in background. Well, not really but there is some code running in background which says "Mii Maker will be mine" - and when you open Mii Maker, it will boot into homebrew launcher instead. I could be wrong but essentially, a very old method of running homebrew launcher is "installed" into your memory, which will be gone when the console is turned off, and run when specific thing happens (Mii Maker). I said this earlier in thread but this was actually what was done in early, no cold boot hax, no CFW, browser exploits only, destination Mii Maker. Basically you would run browser exploit that would then do homebrew channel "install" and take you back to menu, and for duration of the console staying on you could access homebrew launcher.
I may be wrong with many things, these are user assumptions of not-a-developer not-a-coder not-a-console-exploit-developer, but essentially given we have had CFW for long time, and installables for many homebrew, either forwarder or just straight up installed homebrew (like HBL and WUPinstaller GX2 channel) - the older method of "installing" HBL is obselete, except for the people who have just made up a tiramisu installation and have nothing installed on their Wii U. I am not sure if this is the naming reason entirely; that the Mii Maker HBL packed with Tiramisu is meant for only installing HBL channel on your Wii U drive (Internal/USB) and then yeeted out to not cause further incompatibilities.
TL;DR: It is fine. If you have HBL on your Wii U menu. If not, use Mii Maker to install it, then remove it. Wii Menu HBC is separate and not linked really at all.
