Just noticed this week that the Late 2013 Retina MacBook Pro's Recovery HD is a forked build of 117.
My imaging workflow partitions the disk and was using the Recovery HD image from the Early 2013 Retina MacBook Pro, which is build 116. The Late 2013 machine refused to boot into Recovery HD, however FileVault encryption works fine which is why I didn't catch it during testing.
You can't re-image the Recovery HD volume while FileVault is enabled, so a decrypt of the machine allowed me to re-image the Recovery HD partition with the new build of 117. I was then able to re-enable FileVault on the OS.
This may help some people that are building imaging workflows for the new Late 2013 Retina MacBook Pro machines, and may not think to check the Recovery HD.