But if you are creating a chip that other people will create software for...then you don’t really know.
This is in the context of assessing usage duty cycles of circuits for aging purposes.
I can imagine an era of exploits that rely on "aging out" paths that were assumed to be rarely used. Like rowhammer, but persistent -- fire up a process on a random cloud instance, run a tight loop of code to wear out an exploitable path in e.g. SGX, rinse lather repeat until you have the coverage you need...