I guess that might be a more generic problem for segments using setSqlFilterValue to transform the values.
If a value is provided that isn't included in the list it won't include anything useful I guess.
Might be better to disable any compare that does not match an exact value for those segments maybe.

Otherwise we might need to handle such stuff in a complete other way. E.g. we would need to go through the list of possible values and match them against the segment. The matching ones then would need to be transferred to their SQL value and combined into the sql query according the match type.

We'll eventually add a possibility to only show certain segment comparisons for certain types of dimensions. Eg for boolean dimensions only equals and not equals may be offered etc. So depending what comparisons a segment supports different comparisons will be shown.

United States is not available in the suggestion at all, even though visitors are tracked from United states.

@KarthikRaja1388 what you describe is a duplicate of #15620