When using the parse_evergreen_file() method of the ciconfig.evergreen Python module, if the evergreen_binary parameter is not set to None then the project YAML file is pre-processed using the binary.
This causes the test_lifecycle_excluded_tasks list to be discarded as it is not recognized by the binary.
The lifecycle_task_names property on the created EvergreenClient will then also contain the excluded tasks.

Note that this does not impact the tests analyzed for test lifecycle as they are currently limited to the js_test kind and the excluded tasks are either of a different kind or generate their test files dynamically.