Hi @mrhawk555 ,
IMO this is what we call "flaky" tests - tests that sometimes work and sometimes not.
It is highly discouraged among the tester community to accept flaky tests and it is equally discouraged to handle them by automatic retries.
This is especially true for the kind of tests that are meant to be created with utPLSQL: Assert-based tests, checking deterministic functionality.

I understand your intention and need for such a feature, but utPLSQL is definitely not the right tool for these kinds of performance tests.
I don't know about good performance testing frameworks, maybe one of the peers here knows.

One of the biggest problems that occur with a growing test-base is when they contain mixed-up, not clearly defined types of tests (unit, integration, performance). You will do your team and your future self a big favor by carefully separating and maintaining them.
One option to do so would be to use tags.
You can tag performance-test suites with a performance tag and exclude them during normal runs.
You could then create your CI pipeline in a way that performance tests are run independently, possibly with retries.

I hope this helps,
Samuel