The reason it didn’t end up in macOS is because NetApp sued Sun for patent infringement. Apple wanted nothing to do with that lawsuit and quickly abandoned the project.
As others have stated, dtrace has the exact same license and has been in MacOS for years.
It’s a moderate pain on Linux and then only really that if you’re running on something bleeding-edge like Arch. Otherwise it’s just a kernel module like any other.
A CLA and copyright assignment was how Oracle were able to make (now Oracle) ZFS proprietary again in the first place. As you say though, OpenZFS and Oracle ZFS have diverged quite a bit, and most of the world is now based around the OpenZFS variant that acts as the upstream for Linux, FreeBSD and even Windows variants.
It's a combination of the license and the fact that it's Oracle, of all entities, that owns the copyright. Perhaps either one by itself wouldn't be a dealbreaker but the combination is. And, of course, Oracle could have changed the license at any time after buying Sun.
(Of course, Jobs may have just decided he didn't want to depend on someone else for the MacOS filesystem in any case.)
ADDED: And as others noted, there were also some storage patent-related issues with Sun. So just a lot of potential complications.
I had ZFS on a Mac from Apple for a short amount of time during one of the betas :( I think TimeMachine was going to be based on it but they pulled out.
I used it for a while but unfortunately since they are not many people working on this and they are not working on it full time it can take them a good while from a new version of macOS is released until OpenZFS is usable with that version of macOS. This was certainly the case a while ago and why I stopped using OpenZFS on macOS and went back to only using ZFS on FreeBSD and Linux instead of additionally using it on macOS. So with my Mac computers I only use APFS.
As others have stated, dtrace has the exact same license and has been in MacOS for years.