Currently, the workflow to achieve this is in general case (including canted track) where profile = lower rail elevation is :

1. Create lower rail of branch line: horizontal offset

2. create rails on main: create rails command

3. Extend slope defined by main rails on branch low rail: Profile by variable slope from elements

4. Create profile on branch centerline: Profile by slope or vertical offset from element

Nothing too long or difficult. It could be a single command: create turnout profile. Everything automatically used if known: main CL, main cant (instead of having to create rails), automatic understanding of where the lower rail is and what the CL profile must be based on rotation point, maybe a parameter that must be exposed.

We may create the cant as well but more difficult to manage all cases. Typically, the branch complex that is holding the cant may not exists at that step. Should we store cant in the turnout so that it can be used when creating cant on branch ?
Maybe the cant command used on a branch that includes a turnout should be able to use any known information without asking the user to project cant or manage cant manually.

Projected "turnout" cant points (.3 and LLS) from main should be automatically created in branch cant alignment.

Let's create another idea for that cant enhancement.