Guess it really is possible, Matching JA4 using only net.Socket.
It would be really cool if this was built on further. I handle all tls1.3 ciphers but fake support for X25519MLKEM768, no tls1.2 fallback, no session resumption, no certificate validation, no http/1.1 support, and just a very basic h2 request to get the response, it's also very slow
Turns out you can mimic the chrome tls fingerprint in Node if you write your own TLS client over net.Socket rather than using their internal openssl bindings