Indeed! However, getting edge softening to work has value as follows:
Since Rhino is weak at fillets, often not an option inside Rhino. Must go to MCAD app to get the fillets in without failure. Boohoo.
Now that the data, with fillets, is outside Rhino, might as well render outside too, i.e., Keyshot, etc., as opposed to re-import with fillets. Especially when rendering simply for design evaluation. This whole ordeal is rather inefficient, though.
Played, briefly, with V6 WIP and Cycles. (focused on MacRhino) Has promise, especially for nice RT photoreal views, while designing. It is a lot slower than Keyshot to come into enough focus to move on, but staying in Rhino is a lot faster than moving to KS just to have a photorealistic look at design progress.
To avoid the aforementioned hoop jumps, and when fillets fail, functional edge softening allows one to remaining in Rhino when desiring an accurate look at progress. Valuable. Obviously, such is perpetual and ongoing.