I’m going to take a wild guess here and say that it is probably a security setting on the Mac side at fault.
On the hotel side, what’s happening is that if it hasn’t seen your WiFi device’s MAC address before (or outside of the timeout), it will replace whatever page you go to with the sign-in page. As you’ve found, once you sign in on any browser, or any OS, you’ll have continued access from the same device (since it’s detecting your hardware, not OS configuration).
But replacing one page with another is a security concern. It could be a means of harvesting passwords, etc. (a type of phishing). Plus, modern browsers tend to automatically use HTTPS instead of HTTP when available. A substitute page probably won’t be HTTPS at all, and even if it was, it would have the wrong certificate.
Windows is probably either ignoring that security hole, or more likely, has some bypass to allow this particular situation to work, and the Mac isn’t doing that.
Some of these settings can be adjusted. For instance, you can try deleting some domain from the Chrome domain security policy page:
chrome://net-internals/#hsts
Then try visiting the HTTP version of that page. Probably doesn’t matter what you try. You may also just visit some domain you haven’t been to before so it doesn’t have any existing settings.
If that doesn’t do it… well, I dunno, but you may just futz around with the MacOS internet security settings. Maybe there’s a global option you can disable. I’m not familiar with MacOS and how it handles this stuff.
In short, as long as hotels use this type of sign-on redirection, there’s likely nothing they can do. It sure as heck isn’t the fault of the hotel staff. And it’s obviously not homegrown; every hotel or airport I’ve been at clearly uses one of the same few varieties of software, with the only difference being the look of the landing page. It’s the Mac that should be handling it better.