We did essentially that at my employer. I think the rationale is good, biasing toward a secure random function makes sense because the downside (as I understand

We did essentially that at my employer. I think the rationale is good, biasing toward a secure random function makes sense because the downside (as I understand it) is performance, but defaulting to insecure random has worse downsides. And if there ends up being a hot path where secure random is too inefficient, you can change it in that case. (This is in a context where a secure random function is readily at hand, when that's not the case, it could be trickier.)