The risk is, by asking, you indicate you don't know how to use standard industry tooling.
"hey, your starter code is not running in my environment, have any documentation about how to set it up" is a better question to ask when it's some custom script they hacked together.
But if that's actually the problem, then it's in the best interest of both the employer and the applicant that they not be hired. The applicant isn't ready, and is likely to have a miserable time on the job.
This kind of wordplay makes sense from HR's perspective. Ex: it "wouldn't be a fit for you anyway", there are "other jobs where you'll be able to grow more", etc.
The best interest of the applicant is always to get an offer (or stop the interview process of their own volition). Not get rejected by a screen and get zero feedback. Obviously this costs more for the business, which is why they have incentive to use that kind of reasoning.
Even if you shouldn't take it, competing offers can be used in various negotiations. And getting practice at interviewing is how you get better at interviewing (and at your actual job).
I don't think this is a controversial statement. If such an applicant gets the job, both the applicant and the employer will be unhappy and someone will either have to quit or be fired, which also sucks for all concerned.
> If such an applicant gets a job...
Getting the job offer would not cause any of those problems. By getting it you would build valuable interviewing experience. Taking it is the thing that's not in your interest. That's all I'm trying to say.