Okay, we have that already so we’re mostly good there.
it’s difficult to untangle, but with relational databases like the ones iNat presumably uses, it isn’t logisically impossible at all.
I mean that with the way the taxonomy system is programmed currently, it’s literally impossible for one species to be a daughter taxon of multiple parent taxa. It has to be a branching tree, there can’t be one leaf growing out of two different twigs.
That does cause issues in braided stream situations (like I think Eastern Tiger Salamander is part of both the tiger salamander complex and the unisexual salamander complex) but those situations are apparently rare enough to not be worth completely redesigning the whole system (which could take a huge amount of thought and effort) when there are many higher priority development goals. Kind of like sharing observations where that feature request won’t be implemented for a long time (if ever) because it apparently would require a rethinking of the fundamental philosophy of what an “observation” is.