It could be that your replace section that adds the real_ip for your reverse proxy(?) is conflicting with the cloudflare template since they both do similar things. You need to make sure that the user IP and not cloudflare’s and not your reverse proxy is what Discourse sees. My best guess is that this is why the rate limiting template won’t work. You will likely need to fix that as right now all traffic is coming from your local IP.
The AMD servers are a little bit faster than the Intels (but I don’t they don’t have dedicated CPU for those? So Intel might be preferred?)