That car analogy is perfect, that's exactly how it feels sometimes.
You mentioned trying to get analysts to use it for a new product launch and it didn't stick. I'm curious, what were the "old habits and separate tools" they went back to? I'm asking because I've seen this happen when the new platform is presented as a complete replacement.
Instead of replacing their whole toolkit, maybe there's a way to slot RF in as a final verification step? Like, they do their initial research the way they always do, but the policy requires that any external vendor domain or IP in the final assessment has a corresponding RF report attached. It makes it a non-negotiable part of the deliverable, not a new way to work. That's worked better for us than asking people to change their entire process.