FYI Google are now tracking this as a Chrome issue here: https://bugs.chromium.org/p/chromium/issues/detail?id=1014614
It looks like it might be possible to override the base latency, but it creates an awkward problem. Firstly this is only necessary for Android; secondly if you specify too low a value on a device that really doesn't support it, you could end up with lots of audio glitches, which is worse. So using that is like rolling the dice and randomly making it either better or worse. I'm always skeptical of implementing any such measures, since we can expect the next bug report to be "when I set a low custom latency, some devices have awful audio glitches", and they'd expect us to fix that... which means going back to where we started.