Update: I initially thought this U-shaped configuration could not be created as a single VisualARQ Stair. After further testing, I found that individual flights and landings can be edited through the Stair Object Properties, which makes this configuration possible.
The remaining issue is the lack of independent control over the start and end condition of each flight, and the most problematic is the U-shaped stair.
Required flight-to-landing configurations
A U-shaped Stair object should allow independent control over the start and end condition of each flight, covering the three configurations shown below.
U-shaped stair example
The Stair object currently determines how the flights start and end, without providing independent start/end tread control for each flight.
The three configurations above are basic variations that should be selectable independently for each flight.
For instance, Type 2, with the risers aligned with the landing edges, is a very common configuration, especially in compact buildings where the available space for the staircase is limited.
The top flight end condition is also important, and is discussed in more detail here:
[Stair last step subtraction error + documentation tips]