What resources will the reverse (reverse) proxy require?

Question

Nginx

There is a problem to hide one site (not to show its real IP)
I understand that this can be easily solved (as one of the options) using a reverse proxy on nginx
There are several questions:
1. What resources will the reverse itself require? Maximum 2000 uniques per day, I want to buy the most inexpensive vps in the Russian Federation and implement it on it.
2. If the real site is not located in the Russian Federation and there are 16 jumps on the traceroute before it, then it will be possible to drive a lot of traffic back and forth, right? To what extent will these delays be visually noticeable to users? Basically average hop 20ms

Answer 1

1. It consumes very little, the minimum vps is enough for several similar ones.
2. 2000 uniques on average generate very little traffic. The delay will be the sum from the origin site to the reverse proxy and from the reverse proxy to the end user.
Threat and for "hide" it is enough to place it behind cloudflare

Answer 2

delay from the elementary ping plus to the correction on the incoming channel curve to the masked VPS

Answer 3

Static and caching - pull out a double on the reverse proxy, and leave the API for the database and scripts for working with the database on the real IP.
For a banal reading of the site - it will be fast.
The rest - users will survive calmly, tk. exchange with real IP will be only when the data in the database changes.