Test effect of database polling instead of oplog tailing in dev mode

So, we know that Meteor can get overloaded with oplog messages and as a result can fall back to database polling.

I would like to test how this feels like in development mode (since I guess this means messages could arrive out-of-order, UI might need more loading indicators etc.)

I know we can disable oplog tailing (even per-query), but this doesn’t change anything if there’s only one instance so the subscription and mutation methods are ran on the same instance.

So does anybody know of an easy way to simulate this in development mode?