The transceivers would probably be surfaced after setRemoteDescription anyway and ontrack should fire regardless. Applications that don't think about sdpSemantics would probably not notice the fact that transceivers are not surfaced directly (they would not even use getTransceivers()) so this is not a dealbreaker for Unified Plan.

It's a real bug though and it's not entirely clear if this could cause other unexpected behaviors.