That misunderstanding is something that causes a lot of grief in SAP introductions.
When working with large enterprise software, customization is your enemy - and every time you have to customize something there, you should ask yourself if you shouldn't re-think your business processes instead. Often enough IBM, SAP or whatever have considerably more experience than you.
So when it came time to think about next steps. There was real appeal in being able to say, "No it's not supported in xyz software we just adopted". This prevents us from looking like the bad guy who's just getting in the way and should be laid off because we didn't want to spend 2 months implementing a hair brained idea that would only give us a net return of like four or five thousand dollars.
This is my thought about all these efforts. The mammoth people talk like it's about a solution to climate change, but that's obviously working backwards from their goal (revive the mammoth for reasons) to some sort of reasonable-sounding justification. They set out with different motivations in mind.
I'd ask the same question here: why try to bring back a species we already killed off? These won't be descendants of the animals we killed, so it's hardly a form of reparations. If it's about preserving the ecosystems we already have, there have to be more efficient ways to do that than rebreeding less stripe zebras.
It's hard not to see this as just the same impulse that led to the poodle: because we can and because it will look cool and draw attention and make money. The only difference is there's a slight nostalgic bent to the aesthetic.
Deleted Comment