Currently we exclude every test marked with requires_profiling from being run in any replica_sets_jscore* suites, adding up to a substantial loss of coverage (currently 39 tests excluded from 36 suites). 

Most of the tests seem to finish successfully when ran with --force-excluded-tests, but according to the investigation in BF-30849 they may experience intermittent failures due to additional listIndexes commands emitted by a background process. 

One alternative fix to this issue (as opposed to the base suite exclusion) could be fixing the problematic tests by filtering out commands emitted by background threads similar to the following:

// Don't profile the setFCV command, which could be run during this test in the
// fcv_upgrade_downgrade_replica_sets_jscore_passthrough suite.
assert.commandWorked(
    testDB.setProfilingLevel(1, {filter: {"command.setFeatureCompatibilityVersion": {"$exists": false}}}),
); 

Reference