TL;DR
I'm closing this ticket as I figured out the workaround. I used KiTTY (like PUTTY, but stays connected ... or reconnects faster). I was able to interrupt the boot, and perform a factory reset that way. After that it took a while to setup a TFTP Server correctly, then updated the firmware through the console port. I did notice it detects the SFP plugged in and changes the port speed based on the SFP (which is still a problem if you don't have a 1000M to RJ45 SFP, or similar device). Since I had that (no provided by TP-Link), I logged into Omada, and provisioned the device (it still disconnected at first). I manually restarted the switch, and it came back up.

Additional Info for TP-Link:

After ALL that, I got it to work. But TP-Link please take this advice as more and more of us non-business class users WILL need TP-Link to auto-negotiate the link speed. If TP-Link fails to see this as an issue moving forward, you will fall behind in sales of 10G or fiber devices for the everyday residential user (maybe that's not really your market, but I feel it is as I use it in my home). I hope you take that feedback wholeheartedly as I currently love your hardware, software, and company. Seeing Clive_A replied so quickly gave me hope. I'm sure Clive_A would've helped me solve it, but I have technical knowledge that allowed me to keep pushing for the fix on my own more quickly.