Feature: tag performance event if any stops on breakpoints

Hi. I sometimes have Sentry enabled while running locally (setting environment: 'localdev'), and the performance logs that this collects are skewed by those sessions where I had a debugger enabled (in Chrome, in my case) and stopped at a breakpoint, leading to transactions artificially taking minutes or hours. It seems to me that this can probably cause noise for client-side performance monitoring in production as well, when end users use their browser debugger to poke around. Is there a way to get transactions automatically tagged with e.g. breakpoint or debugging if there was any stop at a breakpoint during the transaction, so that we can then filter out those transactions when browsing Performance transactions? (Or alternatively have an option to not send those transactions in the first place?)