In CI (Github Actions) , as generally is recommended I have limited with max-workers=1. With a single worker 5 min doesn't sound it unreasonably long for 2,000 tests? Most CI runners are going to only give lower performance single core vCPU in their runtime so it doesn't seem too bad time taken for this type of workload.
On my laptop I run 6 tests in parallel. It runs in 60ish seconds however the balance is how much cores I can spare for the workers while still being able to do something else.
The challenge is if you switch to another task you don't come back always after the minute and it takes some time to review and commit, or some tests failed now you are fixing those and also working on other items.
Both tasks go poorly, because after each run you want to go back to other task so sometimes you fix one thing and that breaks something else in the next run, so you keep doing few runs and that new task is going poorly because you are losing focus constantly, the
Or eventually you end up with work that is really few completely different commits getting actually pushed as one big item, If you like frequent atomic commits this is just breaks your flow all the time.
P.S. the pet peeve: when the laptop fans starts spinning hard to handle the work, it feels like the same frustration that I feel when I am out of shape and start huffing and puffing in a simple 2k run.