@Dave_Lee - Chromium detects whether any NRPT rules have been configured and if so takes that into account in a few places, but it does not, itself, utilize the NRPT tables.
However, I'm interested in learning more about your scenario. On Windows, by default, Chromium uses the system's DNS resolver (instead of using its own built-in resolver) and that means that the NRPT tables should be taken into account. If you're seeing something else, I'd be interested in learning more.
[In Edge, you can see the details of DNS resolutions for the current process by visiting edge://histograms/Net.DNS.TotalTimeTyped in the address bar. If you see a Net.DNS.TotalTimeTyped.System histogram, that means that the system resolver is getting used. IF you see instead Net.DNS.TotalTimeTyped.Async that means that the built-in (non-system) resolver is getting used.]
We cannot use "Force Tunnelling" as we use S4B voice which cannot go through the DA tunnel.
At the moment, only IE 11 and old Edge read the NRPT tables. Chrome, Firefox and Edge Chromium ignore the entries we've made.
Here is the scenario - We have many hosted services that are locked down to our two corporate, public facing IP's. Any attempt to access these services over other connections will not work, i.e. on DA when working remotely. Via the use of NRPT table manipulation and Selective Tunnelling, we can make these services available to our remote users as we force the traffic back down the DA tunnel and out of our corporate DIA's.