Hi Rob,
that is a general sim issue and that´s exactly the point, why 3rd party developer shouldn´t use the FSX bgl in-game navdata files.
The problem are the runways - in MSFS (stock scenery) you have only 2 runways 16/34 and 10R/28L:
In reality you have 3 runways 16/34, 10R/28L and 10L/28R - now, when the sim can´t assigned a terminal procedure to a runway, the sim disable the procedure (specially the STARs). That´s the reason why you see ie. BAGS1K for 16 because this runway exists in MSFS, but BAGS2Z is for both 10L and 10R - the MSFS can´t assigned the procedure to 10L and therefore it will disabled completely and you can´t select it nowhere.
For PMDG, Fenix, Maddog and a lot of upcoming addons, they will use external databases to be completely independent to the MSFS data logic. In your example with the Fenix screenshot, you see that we have the data and the data are also included in the MSFS data but the logic in the MSFS suppress it. Normally, when you use a 3rd party scenery which is more up2date and which contains all runways you will see all terminal procedures immediately - no update from our side necessary, because the data are still included.
EIDW freeware scenery installed, which includes all runways and here, you see all STAR correctly, like in the Fenix:
Sorry Rob, this is a sim limitation since day one with the in-game data and the MSFS logic behind. Here, we can´t do anything.
Cheers,