Vault uses a fundamentally different model than what you're prescribing:
Instead of managing password rotation on accounts, it creates/removes accounts dynamically as needed. So instead of a user requesting a password, he's actually requesting a full set of credentials. When the "time is up" vault actually removes the account entirely (or invalidates the cert, or whatever depending on the implementation of the dynamic secrets backend).
In this way vault doesn't rotate anything ... instead if generates on demand.
The one big gap, however, is that it doesn't rotate it's OWN credentials it uses to do this. At least last I checked it didn't.