I'm not sure to be honest. But since gis.db.models.aggregates takes over completely from gis.db.models.sql.aggregates, and the sql.aggregates exposes the standard aggregate functions, I copied the strategy from there (which does expose standard aggregate functions).