In T378385, a large influx of flaggedrevs_CacheUpdate jobs led to isolation failure among jobs mapped to the "low-traffic" consumer in changeprop-jobqueue.
While T378609 tracks monitoring improvements to try to detect similar scenarios in the future, we could also proactively shift one or more particularly latency sensitive jobs out of low-traffic into a dedicated consumer (as has already happened for a handful of other jobs, see [0]).
Two such jobs that came up in that context are AssembleUploadChunks and PublishStashedFile, given that execution delay translates directly into waiting at the UI.