If you applied the "Scream" test for a component you don't know what it does in an airplane, it might fall/explode/whatever.
If you do it in a non-critical codebase, it might just break the build, and have someone call you for it.
In the first case, the Chesterton's fence caution is more advisable. In the second, you could go with a "remove it and see what happens" approach.
Option one assumes that you can easily reverse your action with no damage done, which very often isn't the case
If the risk is low it may be simpler/quicker/more cost effective to turn it off and see if anyone screams. So long as you are listening for the scream and can easily turn it back on. Obviously this can be abused but there are times when it is useful.
If the risk is high, definitely spend the time to understand why, even if it is non-obvious.