> (up to and including ‘relying on a Chrome.exe process name’, like, come on)

I would bet this is an application shim of some sort. Hardcoding behavior like this into the shell is risky. Shims often target based on process name and executable path on disk (but can be configured to also match resource info).

I would dig into it, but I cannot repro the issue on Win10.