Thanks for your reply.
Atm, there’s no much reason, but as you’re asking, could think of a few scenarios from the top of the head:
1) If the auto-generated live keys get somehow compromised (they’re stored as-is in the DB), they could be used maliciously, and currently there’s no centralized way to review and make sure they’re destroyed, as they’re out of reach of the Dashboard (which by itself is a very strange thing to be allowed by Stripe, IMHO).
2) Reconnecting the plugin creates new sets of keys (have done it many times already), but it isn’t clear what happens with all those previous keys that are presumably still stored somewhere at Stripe. Those redundant, hidden keys, if still active, could become backdoors for malicious activity, as per p.1.
3) I keep copies of real websites that resolve to localhost for dev purposes. Attempting to (re)connect live-mode in such copies is risking making a mess in the actual websites from the inadvertently changed keys that might have now become invalid.
4) I’m used to store all my sensitive data in one place for reference and for helping me keep it all up to date. That way, I could more easily restore a given plugin etc. w/o having to chase stuff deep down possibly arcane interfaces. Restoring your plugin manually seems currently possible for test-mode only.