This is correct.
Journey Analytics is a behavioral analytics tool
and is only aware of fields if it receives at least one event for a field. This includes
navigation, validation or completion, such as clicking in a field, auto population of a
field or one or more keystrokes to complete the field.
It is not possible with the current architecture of the application to know anything about
fields that are never actually touched by a user.