I dunno … if you’re trading off filter accuracy for completion time … I don’t think there is a solution… different users will want differently.

The “implementation standard” that allows users to subscribe to such an algo SHOULD be able to accomodate “options” sent along with the query.

If a developer is concerned that their algo is loosing users cause it “takes too long” then they could simply provide an option to toggle for speedier results.