I created a DateTime helper for watering our plants every 7 days, and an automation that triggers every evening around dinner time that checks the timestamp in the helper, notifying me to water them if the date has passed.
Whenever I water, the smart switch on the water pump triggers another automation that resets the helper's value to "now + 6.5 days". So I always get the reminder on the 7th day, and if I skip it, it'll nag me the next evening, and the next. If I water a day early, next week I'll get the reminder a day earlier, because it's been 7 days.
Someone recently posted the brilliant observation that NFC tags can be used to track your chores. So now I'm planning to slap an NFC tag on the furnace and create another helper to remind me to change the filter after 90 days. Eventually I can put NFC tags on all the things that need periodic maintenance, and just wave the phone at them when they're done.
Since this seems like a thing that can quickly expand, I'll have to figure out how to rework the automation scripts so I don't have to create two new scripts for every chore. But that's a problem for future me.
In a few instances, yes.
You might find the task of changing a password frequently to be so tedious that you install and learn how to use a password manager properly, and you use it to generate long random passwords that are unique to every site. Changing your password then becomes a few mouse clicks. This will greatly improve your passwords' quality, as well as your overall security.
If a site improves their password hashing and storage systems, when you change your password the newer passwords will be hashed with the better algorithm. Yahoo has done this a couple of times over the decades. It's certainly uncommon.
When a password has been breached but the loss has not yet been discovered or reported, if you happen to change it after the password has been copied but before it is abused by the thieves, you might dodge the bullet. The odds of this particular timing actually happening in a data breach scenario are pretty slim.
The more likely case is that a password is shared with (or learned by) a coworker who abuses it. Rotating passwords in sensitive positions after a personnel change is a prudent policy.
Note that these two scenarios are literally the only justification ever raised in favor of password rotation policies.
Otherwise it has no effect on Confidentiality or Integrity, and a slightly negative impact on Availability as people often forget their new passwords, or waste productive work time dealing with password changes.