Nuke ACES Output Transform and a Question

No. As @Thomas_Mansencal said, you can get close but there’s not enough degrees of flexibility (by design!) to match all the weirdnesses of the SDR RRT+ODT tonescales.
I used the 1.1 HDR transform revisions to demonstrate a different and more flexible approach to make “automatic” creation of tonescales for dynamic ranges other than those that ship with the pre-made transforms more intuitive and, more importantly, repeatable.

We couldn’t overhaul the SDR to use the same algorithm without changing the “look” - which would have required a major version bump to 2.0. But there are many other simplifications that we want to work into 2.0 and we were not at a phase to tackle those yet so we left the SDR transforms untouched.

This thread has a little bit of discussion around the SSTS approach when I was first proposing it to the HDR ODT Virtual Working Group:

I think yes, the SSTS in some form will be used. It almost certainly won’t use the current parameters but I think the philosophy is more robust than the separate RRT+ODT tonescales. The SSTS is much more intuitive and flexible without allowing the user to “create their own shape”. By that, I mean it’s a technical rendering curve, not a creative one. So if you put in the same display parameters, you get an Output Transform with an identical tonescale every time. Figuring all this out will all be part of the ACES 2.0 Output Transform work - which I expect will be forming soon, so if you have an interest in this - I suggest you look out for that announcement and join in the discussion if you want. It is open to all!