Happy Eyeballs cannot be implemented in libc/Winsock/etc. alone, because it crosses the abstraction barrier of the Berkeley socket API. Happy Eyeballs wants you to open two TCP connections to the same hostname, one over IPv4 and one over IPv6, and use the one that returns an ACK first. But the BSD socket API separates the process of looking up the hostname and opening a connection to it - getaddrinfo() returns a list of addresses, but you can only pass a single address, with a specific address family (IPv4 or IPv6), to connect(). So the intended use is that the application iterates over the returned addresses itself. You could come up with some scheme where libc caches the IPv4 and IPv6 results and has getaddrinfo() return a fake address to the application that's actually an index into the cache, and have libc implement Happy Eyeballs on its end once connect() is called, but that would probably have all sorts of negative side effects, starting with the fact that getaddrinfo() couldn't be used for any other purpose than generating addresses for connect().
Also, not every protocol is compatible with Happy Eyeballs, because there's no guarantee that opening a connection is harmless. It's perfectly valid for me to e.g. implement a smart lightbulb protocol by having it toggle off/on when it receives a connection from a trusted network interface without actually requiring data to be sent. If you used Happy Eyeballs in this case and both IPv4 and IPv6 worked, you wouldn't be able to turn on your lights. This is of course a contrived example, but the authors of generic libraries like your libc have to worry about contrived examples.
So it has to be implemented by application software or at least a library for the specific protocol like HTTP (layer 5 or up), which means that in practice, lots of apps won't have it implemented. And therefore in practice, broken or degraded IPv6 is very end-user visible.