Yes. In practice, users will selectively enable JS, both intentionally (because so many sites require JS, to be minimally usable), and accidentally because the particular JS-disabling add-on that TB currently uses still has a complicated UI (though it's much improved from earlier).
(I made one of the early tracker-blocking rulesets, and, for the last few years, as a side project, have been building a new practical dataset of specific sites' JS dependencies and third-party requests. I'm up to over 10,000 necessary whitelist rules, which I add to throughout each day, in my own normal use. That 10,000 doesn't include blanket whitelisting of many popular JS CDN URLs, for all domains, which I eventually had to do because of current tool support, and most sites needed them, and there's something privacy&security-friendly that could be done in the browser about those URLs in particular.)
(I made one of the early tracker-blocking rulesets, and, for the last few years, as a side project, have been building a new practical dataset of specific sites' JS dependencies and third-party requests. I'm up to over 10,000 necessary whitelist rules, which I add to throughout each day, in my own normal use. That 10,000 doesn't include blanket whitelisting of many popular JS CDN URLs, for all domains, which I eventually had to do because of current tool support, and most sites needed them, and there's something privacy&security-friendly that could be done in the browser about those URLs in particular.)