I'm sorry for the confusion.
Your initial post sounded to me like all entries were 2018, but most have just been added.
Indeed not all entries might affect each Firefox version. Since the profile cannot easily and safely be linked to a specific version, we always immunize all.
Some are also "flexible" - think about browser.safebrwosing.provider.*.gethashURL and .updateURL for example. They're only existing after SafeBrowsing has been used in our test case.
If you've got both BrowsAlyzer and Anti-Beacon installed, BrowsAlyzer will match entries in the various Mozilla config files to Anti-Beacons database in a simply overview. But that does of course not include what Firefox shows as undefined with default.