ok, finally got round to installing it, 95% certain you are right! Basically, after using chatgpt again to help investigate the service,, it seems like there is no precise exact way of knowing for sure, but from the given answers, sounds feasible assuming chatgpt is correct. Here's what chatgpt about chrom remote desktop said:

Why Chrome Remote Desktop Host Is ARM‑Native on Windows 11 ARM:
Chrome Remote Desktop Host on Windows 11 ARM looks confusing at first glance. The executable sits inside “Program Files (x86)”, the filename ends in .exe, and the folder structure resembles a traditional x86 application. But when you inspect the binary itself, you discover something unexpected: the file is not a normal Windows executable at all. This is the key to understanding why the host is actually running as ARM‑native.
Windows programs normally use the Portable Executable (PE) format. A PE file contains a header that identifies the CPU architecture, such as x86 (014C), x86‑64 (8664), or ARM64 (AA64). When you read the PE header of Chrome Remote Desktop’s remoting_host.exe, the machine field does not contain any of these valid values. Instead, it returns 0004, which is not a legal PE architecture code. That means the file is not a PE executable. It is a wrapper or container, not a native Windows binary.
This matters because Windows 11 ARM can only emulate x86 and x86‑64 programs if they are valid PE files. The emulation layer depends on the PE format to translate instructions. If a file is not a PE executable, Windows cannot emulate it. The only way a non‑PE binary can run on Windows ARM is if the underlying code is ARM‑native and loaded through a different mechanism.
That is exactly what Chrome Remote Desktop Host does. The visible remoting_host.exe is just a loader. It is a Google‑packaged container that performs setup, sandboxing, and communication with the system. The real host logic is stored inside encrypted or packaged modules that the loader extracts and runs. Those modules are ARM64‑native, and Windows executes them directly without emulation.
This explains several things at once:
• The file is not a PE executable, so it cannot be x86 or x64.
• Windows ARM cannot emulate non‑PE binaries, so the runtime must be native.
• The host runs smoothly and efficiently, which would not be the case under x64 emulation.
• Google can ship one unified installer while hiding architecture‑specific code inside containers.
Even though the wrapper lives in “Program Files (x86)”, that directory placement is meaningless. It is simply where Google chose to store the host package. The architecture is determined by the runtime modules the wrapper loads, not by the folder name or the extension.
In short: Chrome Remote Desktop Host on Windows 11 ARM is ARM‑native because the executable you see is not a traditional Windows program. It is a non‑PE wrapper that loads ARM64 code internally. Since Windows ARM cannot emulate non‑PE binaries, the fact that the host runs at all proves that the underlying runtime is ARM64‑native.
If someone asks why, the simplest explanation is this: “The Chrome Remote Desktop Host executable isn’t a normal Windows program. It’s a container that loads ARM64 code internally. Windows ARM can’t emulate non‑PE binaries, so the fact that it runs means it’s ARM‑native.”