I don't think we can really compute the best settings based in file version (1.75, 1.76...). Because it's current status (and you don't know when that status was acquired). Is possible that someone running 1.76 now has been running 1.75 for months and just updated 1 week ago, for example. And all sort of combinations.
So, definitively: -1 to make cvs version based checks IMO.
I think that we should, simply:
1) Apply the module patch. This way both settings will be working ok in the future.
2) Comment in the database module forum.
3) In upgrade, query DB to see if there were activities using only one of the settings. Those are the sites that will need review. Warn in upgrade (perhaps showing list).
That way, functionality will be working ok in all sites. And sites will have a chance to review their configuration in some activities.
I cannot imagine another way to compute the different versions mesh