Using this attribute causes excessive padding depending on the amount of hidden fields before the current field being show.
This is the tested code:

Here is the result using the Test1 enum, no visible issues:

Here is the result using the Test2 enum, you can already see a small padding separation between "Heart to affect" and "Heart Type to swap 2":

Here is the result using the Test3 enum, you can clearly see a huge gap between the remaining fields:

This is not affected by the amount of enum values, it is affected by the amount of fields that are shown/hidden. It would seem there is a strange addition of height somewhere that takes into consideration all fields affected in the target. I tried to look it up myself but was unable to locate the proper logic.