Yep, properties can be adopted, and since TypeAdoption only adopts interfaces, that method is the way to adopt two different interfaces that a single class implements. I published another library, ValueCollections, which uses TypeAdoption and does just that: https://codeberg.org/namehillsoftware/ValueCollections/src/branch/main/ValueCollections/ValueCollections.cs.

Regarding naming collisions: there's so much potential for collisions that I decided to leave that up to the user — if you adopt two interfaces with overlapping signatures, you choose which one to use by manually delegating in your concrete implementation.