This sentiment is totally untrue and is why the password resets in PHP apps are the subjects of security conference presentations.
It can be surprisingly tricky to predict which random values an application uses will end up being security-critical.
But a good CSPRNG has excellent statistical properties. So if you make "unpredictability" a requirement, their slow PRNG becomes very attractive. In other words, they made up a problem for their solution.
If you need a statistical PRNG, use a statistical PRNG. (The best are xorshift1024* and xorshift128+.) If you need a CSPRNG, use a CSPRNG.