So I tap the Repeat Password control and the app repeats my password for me?
That’s the problem: when all your controls look the same then the user doesn’t know for sure how to interact with them anymore. You either have to include text instructions, which consume space and slow the user, or the user has to stop and think about how to use your interface (“Hmm, it already says Female and Male, so I guess I select one rather than type something in, and I guess it sets a field, but maybe it takes me to a separate page for additional Sex information… I guess I’ll just have to find out”). You have a TAMIDS interface: Tap Anywhere; Maybe It Does Something.
Different controls should look different. Controls like text boxes should look like standard text box controls, controls with radio-button behavior should look like standard radio buttons, controls with check box behavior should look like standard check boxes, etc. Standard appearances should be used in order to leverage user experience so users can anticipate the behavior. I wouldn't recommend non-standard appearances even if they do distinguish the controls because then the user has to go through the effort of learning the new "code." How close to the standard does the appearance have to be? Close enough to be instantly recognized. For a radio button just about any circle with a dot inside should do, but generally the easiest and safest approach is to go with the control's default appearance.
I don’t see any advantage to making these radio buttons look like text fields. At least in the desktop world, the caption as well as the radio button itself is sensitive to input, so it’s not a issue of target size. Even if testing shows no detriment to response time to selecting sex in your case, failing to abide by standards undermines their usefulness, making it more likely users will be confused in other situations when it’s more ambiguous.