FR: ThreadPool::setDefaultThreadPriority

I’ve noticed that under certain conditions, running background threads can cause the UI to lag/stutter on Windows (haven’t tested the same app on Mac, yet), because both threads share the same priority. If I simply call

Thread::setCurrentThreadPriority (3);

as my first line of code within the job, then the lag/stutters go away.

Would it be possible to have a function that sets the default thread priority for all new jobs in a ThreadPool, so I can’t accidentally forget to set it myself within the job later?

Already running jobs should stay unaffected (we’ve got a function for that already), only newly created jobs would get the default priority.