when you:

sockopen -e test site.com 443

it doesnt work (use to though)

Now it requires:

sockopen -e46 test site.com 443

Bug maybe?

If you're using /sockopen on an ipv4 domain name from a /server -6 connection, -6 completely disables ipv4 for that connection, what's the error message you get?
The -4 switch is there to force ipv4 back in this case, so it's normal.
To get ipv4 to work, you need to use the ipv6 setting which gives priority to ipv6 without disabling ipv4 (use global mode and stop using the -6 switch in /server): https://en.wikichip.org/wiki/mirc/ipv6

Thanks for your bug report. Please include a short script that I can use to reproduce this issue.

Update: I just tried https://site.com:443 in Firefox and the connection keeps failing and timing out.