Be careful with doing this. X-Real-IP and X-Forwarded-For are good for when the client is a trusted proxy, but can be easily faked if you don’t whitelist who’s allowed to use those headers. Somebody with IPv6 access could send “X-Real-IP: 127.0.0.1” or something and if the server believes it then you’ll see 127.0.0.1 in logs and depending on what you’re running the user may gain special permissions.
Also be careful with the opposite problem. If your server doesn’t trust the proxy, it will show the VPS IP in logs, and if you’re running something like fail2ban you’ll end up blocking your VPS and then nobody will be able to connect over IPv4.
ChromeOS and ChromiumOS are Linux.
The problem with ChromeOS (and Android) devices is that hardware support is usually only available in a fork of Linux which gets as little maintenance as possible for the five years. You end up with the choice of running and old kernel that supports the hardware but not some new software, a new kernel that supports new software but the hardware doesn’t work right, or taking over maintenance of the fork yourself. The same problem occurs with uncommon hardware on non-ChromeOS devices.