Currently the component is unable to display self-referencing N:N relationships (when an entity has an N:N to itself) due to the field names being different in the intersect entity. This causes the FetchXml queries and dropdown logic to break.
In a standard intersect entity the ID fields for the respective entities are always named following the pattern '{entityname}id' (for example) 'new_entityid' and 'accountid', this is assumed and implemented in the component.
However with a self-referencing N:N, the intersect entity can not contain two fields named '{entityname}id', the Dataverse auto-corrects for this by using a different pattern, namely: '{entityname}idone' for the left side and '{entityname}idtwo' for the right side of the relationship.
I've created this issue to attach a PR to address this issue :-)