TagPicker and InteractionTag Incompatibility?

[kfallstrom]

In the current documentation, TagPicker lists among its "Dont's" -

Don't use InteractionTag with TagPicker as it is not supported at the moment. This combination may lead to unexpected behavior.

However, when I use a TagGroup, and InteractionTag(s) inside a TagPicker, it seems to behave as expected. The main difference seems to be that TagPickerGroup seems tighter integrated with Tag but otherwise I can't see any issues arising.

Sample code:

<TagPicker >
            <TagPickerControl>
                {currentValue?.id && (
                    <TagGroup
                        onDismiss={removeItem}
                    >
                        <InteractionTag key={currentValue.id} value={currentValue.id}>
                            <InteractionTagPrimary
                                onClick={(e) => clickAction(e)}
                                hasSecondaryAction={true}
                            >
                                {currentValue?.name}
                            </InteractionTagPrimary>

                            <InteractionTagSecondary aria-label="remove" />
                        </InteractionTag>

                    </TagGroup>)

                }

            </TagPickerControl>
            <TagPickerInput value={query} onChange={(e) => setQuery(e.target.value)} />
            <TagPickerList>{renderOptions()}</TagPickerList>
</TagPicker>

We are writing a composite component that we'd like to back with TagPicker, but we also need the interaction part of InteractionTagPrimary to allow for other interactions than just being dismissable.

Does anyone have any indications about future compatibility of InteractionTag// TagPicker? Or, alternatively, could someone spell out some of the "unexpected behavior" that they may have experienced doing a similar integration?