As far as I recall, regionprops() has never had a Rotation property, and even if it did, that wouldn't be how it's invoked. Let's assume that what's meant is either Orientation or one of the Feret angles. Either way, neither are relevant. Given an arbitrary image which has been rotated, none of its current properties inform us of its original properties -- unless there are reliably identifiable features which can tell us about the original orientation.
So are there reliably identifiable features? It's easy to come up with a counterexample.
What is the rotation of this character? 3 degrees? 5 degrees?
The answer is 0.
What about this one? It's about the same, so I'm probably playing the same trick, right?
No, that's rotated 17.8 degrees.
Okay, fine. That's only difficult because there aren't any straight lines or cusps to work with. How about something easy?
Is that 0 degrees or 2 degrees? If we don't have the original image, then I'm assuming we also don't have any other sort of prior knowledge. Even if we know that the straight edge on this L is at 80 degrees, we don't know what it was originally. We have no idea where the cusps were with relation to each other either.
There are no magical universal properties embedded in images of text which inform us of their intended geometry or alignment. Unless we have intimate familiarity with the font, we can only guess at the intended orientation of features or even basic things like em height.
When we only have a single character, then there's even less information. Should we even assume that we know what the font is based on a single character?
When we're working with a character that's only a few pixels tall and has been subject to nearest-neighbor interpolation, it's just that much worse.