Hi Steve,
I am not sure about your use case. Is the information which fields are mandatory and which are not only configured in the UI? Usually such information is derived from the backend which "knows" which input it needs to be filled. Then the UI field properties are either automatically set from the backend information or they are additionally configured. In any case the backend should be the source of truth, not the UI. What you described sounds vice versa. In thas case: It is possible to read GUIBB configurations at runtime, but I would not recommend this. If it is about freestyle WD components, this is indeed a pure WDA topic, but it will be hard to access non-instantiated components.
Regards,
Jens