There are six (6) replication-related fuzzer Evergreen tasks:

1. rollback_fuzzer
2. rollback_fuzzer_unclean_shutdowns
3. rollback_fuzzer_clean_shutdowns
4. rollback_multiversion_fuzzer
5. initial_sync_fuzzer
6. initial_sync_multiversion_fuzzer

There haven't been any novel BF tickets from these Evergreen tasks in the last ~6 months (possibly even longer). Furthermore, it is relatively rare for patch builds to break these fuzzers and when they do it is typically because all of the rollback_fuzzer* Evergreen tasks break at once. While it is important to continue to running both kinds of the replication fuzzers in patch builds to ensure the RollbackTest, RollbackTestDeluxe, and InitialSyncTest fixtures and other dependencies do not change without 10gen/jstestfuzz being updated, it isn't necessary to run all of these Evergreen tasks to provide that stability.

The proposal here is to only run the rollback_fuzzer and the initial_sync_fuzzer in patch builds.