[Noob Asks] Why not giving the Client the public key or the certificate? Does Reality do that (It seems to be this)?

[mostafaid3]

I was playing with my VPS. It has a clean IP. I was wondering about how two computers send and receive encrypted data. I used python to make a program to send and receive encrypted data over both TCP and UDP. Then I started communicating with my VPS server. Also I had an Xray service on that VPS. The config which Xray service was using was VLESS+TCP+XTLS+VISION.
There's a problem with the Xray service. Assume that your going to view multiple Instagram stories or Whatsapp status. I'm not sure about this but it seems for each Request to view the story, a TLS handshake is needed. When I test the TLS handshake with v2rayNG or v2rayN or any other client, it's above 2 seconds all the time. It means that for each story or status I have to wait for 2 seconds at least. It slows down the user experience and sometime makes user angry.
Then I send and receive messages over my own python program, and there's no need for a handshake because the client has the public key. The only configuration which has this low amount of latency is Reality.
What's wrong here? Is that Reality gives the client the public key at the beginning? What makes VLESS+TCP+XTLS+VISION too slow at many times? Can't we just give the client the public key at the first place? The main point is I want to remove the problem of doing a handshake every time I make a request.