I FINALLY got it working but it would NOT work automatically, it kept hanging up at 0% for me, which isn't a big deal but I just wanted to relay my experience.
So I had to perform the exact same manual procedure that so many have posted already :
1.) First, I downloaded the new SSU (THANK YOU SusanBradleyGESC!!!) https://www.catalog.update.microsoft.com/Search.aspx?q=kb5001078
2.) Next, I already had the KB4601318 but it's here : https://www.catalog.update.microsoft.com/Search.aspx?q=kb4601318
3.) Next I opened a command prompt (CMD)
4.) I performed a NET STOP WUAUSERV (that did not work on two of my servers so I did the following:)
4a.) SC QUERYEX WUAUSERV (to obtain the PID)
4b.) TASKKILL /F /PID xxxx (where XXXX is the PID from the command from step 4a)
5.) RENAME %windir%\SoftwareDistribution SoftwareDistribution.bak
6.) I ran the new SSU KB5001078 (this run took about 3-5 minutes)
7.) I immediately ran the Feb security update KB4601318 (this run took about 30-45 minutes)
8.) Reboot (this takes the normal 10 or 15 minutes)
I know this probably isn't the outcome most of us would have liked but at least it was able to run. Honestly, if I had to do this on ALL 50 or so of my servers, I would be absolutely LIVID!
One thing I didn't try (and I should have but I just wanted this to be over and done with already, I mean, I started this at 1 AM and it's almost 5:00 AM and I worked a full 8-5 friggin' day today! Anyway, I'm wondering what would have happened if I would have just renamed the SoftwareDistribution folder and let this month's update run naturally?
Honestly everyone, for me, I tried a bunch of combinations but, ultimately, I honestly think renaming the ENTIRE SoftwareDistribution folder did the trick for me because stopping and starting the WUAUSERV service, running the download locally, running the new SSU, NONE of that was working for me until I ultimately renamed that folder.
Just my 2 cents. Big shout out to everyone that threw out their experiences, thank you so much everybody!