I have just checked this in the nav data and the "D161D" fix does appear in the AIRAC 2301 navdata that is included with the RJ (I haven't checked the latest 2411 cycle but I assume it will too):
Screenshot (48516).png
As far as I'm aware, all of the navaids used by the FMS (and displayed on the ND) are pulled directly from the navdata. We're not creating any additional navaids, or moving any of the existing navaids on procedures, we're just using whatever navaids are listed in the procedure and the coordinates associated with them.
Mark - Just Flight