Is your plan to run some sort of IOT application on the PI?
I'm a little confused as to why you would go through the trouble of running a reverse proxy on a remote server that is fully capable of hosting your web applications and or just setting up a port forwarding rule on your local wifi router to redirect 10080 to 80.
I do a similar thing so I don't have to store sensitive data on a VPS. The sensitive data is used to compute non-sensitive results that I'm happy to go via a VPS.
Is exposing one's residential IP address such a bad thing? Is the threat model just that someone might wish to target you individually, and that they'll have better luck finding a vuln into your LAN if your services are listening directly on public ports?
I bet there are common non default port numbers that people subconsciously tend to use, it might be an interesting project to create a list file similar to a passwd list file to make a port scanner more efficient. GOD = 12345!? 1337
I'd think that using a remote VPN is a better/broader solution to that particular problem. People don't often self-host things at the home, so it's unlikely anyone out there would see my DNS record and assume that it's of value and a useful tool for correlating my IP with my identity (and this actor would need to have eyes on a lot of different services' server logs in order to have data to _maybe_ correlate with me in the first place).
I'm a little confused as to why you would go through the trouble of running a reverse proxy on a remote server that is fully capable of hosting your web applications and or just setting up a port forwarding rule on your local wifi router to redirect 10080 to 80.