Reproduction steps:

1. Open the attached "IN-138996" project
2. Make sure the Profiler is open (Window > Analysis > Profiler)
3. Open the “Assets/SharedAssets/Benchmark/BenchmarkScene.unity” scene
4. Open the Build settings (File > Build Profiles)
5. Under "Platform Settings", check "Development Build" and "Autoconnect Profiler"
6. Build and run the project
7. Observe the Player
8. In the "TerminalScene" section, press the "Stop" button
9. Switch to the Profiler, wait for the spike to appear in the CPU Usage section chart, then stop the Profiler recording
10. Select the frame for the second spike in the chart
11. In the frame view, set it to "Raw Hierarchy" or "Hierarchy" and search for "CreateGPU" in the search field
12. Make sure that on the right of the search field it is set to "Related Data" (otherwise set it to that)
13. Look for entries related to "Graphs/VegetationSSS_Graph" in the "Related Data" section (you may need to move to nearby frames before/after the spike using left/right arrows when CPU Usage is in frame view)
14. Notice it has the keyword "_ENABLE_SSS" present
15. Switch focus back to the Player and close it
16. Switch to the Editor and select the "Benchmark" GameObject in the Hierarchy
17. In the Inspector, find the "Graphics State Collection Manager" component and set its "Mode" to "Warm up"
18. Open the "Collections" dropdown, add a new entry, and select the GraphicsStateCollection generated in "Assets/SharedAssets/GraphicsStateCollections"
19. Switch to the Profiler, press "Clear" at the top, and enable recording
20. Repeat steps 6 through 13
21. Observe the "Keywords" present in the "Related Data"

Actual result: The "_ENABLE_SSS" keyword is present
Expected result: The "_ENABLE_SSS" keyword is missing

Reproducible with: 6000.0.73f1, 6000.3.13f1
Could not test with: 6000.0.0b15 (script errors) 6000.0.0b16 (profiler doesn't connect), 6000.4.3f1 (CS0115 errors), (6000.5.0b4, 6000.6.0a2) (script errors)