It is, because `--remote-debugging-port` is detected via the root DOM object (and that can't be changed unless you want to recompile Chromium), so for example, if you try doing a Google search with debugging enabled, you'll get blocked (usually just by being served a blank page).
Interesting, do you know what exactly changes on said root DOM node in case the remote debugging feature is enabled?
Does remote debugging port itself get detected, or does the presence of a webdriver connection to the port get detected? I believe it's the latter.
I've had success launching the browser and using dumb dumb methods to get around the captcha before attaching playwright.
Dumb dumb methods = wmctrl, xdotool, bash (work fine for Cloudflare's "are you human" check)