Batch Update via Profile for Participant Records : Should freeze or hide custom fields in the grid if they don't apply to a particular row

If a batch update "grid" contains custom field(s) that are "used for" a particular participant "role" (as opposed to all participants) - we should freeze or hide that field for that row. Otherwise, the users get confused because they can ENTER a value in the grid - but they won't see that value when they go to view or edit the record in a singleton context (since that field will be hidden).

I suspect this issue applies to all the batch update via profile implementations (Contributions, Contacts and Participants).