Non-standard port binding - doesn't work for localhost / AGH host

### Prerequisites

- [X] I have checked the Wiki and Discussions and found no answer

- [X] I have searched other issues and found no duplicates

- [X] I want to report a bug and not ask a question

### Operating system type

Linux, Other (please mention the version in the description)

### CPU architecture

64-bit ARM

### Installation

GitHub releases or script from README

### Setup

On one machine

### AdGuard Home version

Latest Edge Release

### Description

AGH is local DNS server only for local clients, not accessible from WAN, not DHCP server, running on Raspberry Pi 4 (Bullseye 64bit), installed directly from https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh .

### What did you do?
Changed binding UDP port 53 to a non-standard UDP port in AdGuardHome.yaml. Router IPTables re-direct all client UDP port 53 packets to that non-standard port. Raspberry Pi IPTables accepts packets on that non-standard UDP port for all clients, except for Raspberry Pi itself, which tries to resolve domains using UDP port 53 and has 127.0.0.1 (localhost) set for nameserver in DHCPCD.conf and in RESOLV.conf. NetworkManager and DNSMasq are not running on Raspberry Pi.

I don't know if this is AGH problem or Linux problem, but how do I force AGH to make DNS queries via non-standard UDP ports for hosts that are running AGH? It just needs to query 127.0.0.1 (localhost) on non-standard UDP ports specified in AdGuardHome.yaml.

RPi is not router and allows only filterings chains for IPTables. Re-direction and pre-routing chains are not functional.

If not possible, then updating Raspberry Pi itself becp,es problematic and requires stopping AGH service, re-configuring AdGuardHome.yaml to bind to default UDP port 53, re-starting AGH service, running Raspberry Pi updates, and stopping AGH service to re-configure/bind AdGuardHome.yaml back to using non-standard UDP port...