Most user friendly way to present exclusive archetypes with nested configuration options

I'm currently implementing a UI for a configuration application. The typical user would be an employee changing the configuration parameters of some client software (like theme, available features to the actual user of the client software, ...).

At some points, the user has to choose one of multiple archetypes (with one being preselected) and can then configure additional settings specific to that archetype.

In other words, the logical layout looks e.g. like this:

General Configuration Page
  │
  │
  └ Archetype Selection
      │
      ├ Archetype A
      │   │
      │   ├ "A" specific setting
      │   │
      │   └ "A" specific setting
      │
      │
      └ Archetype B
          │
          ├ "B" specific setting
          │
          └ "B" specific setting

We currently have this logical layout mapped to the following UI (mockup):

We have a radio button for each archetype and the sub-settings in an additional panel below the corresponding option.

Obviously, the exact parameters of the logical side can change, e.g. more archetypes, or more sub-settings, or some archetypes without sub-settings.

Is this UI layout working out in terms of UX?

What could we improve?