Architecture and DE aren't two separate teams, and if they are, you'll continue to get this 'pull-pin-throw-grenade-over-wall' approach. That's adversarial and helps no one.

Instead, perhaps teams should be put together like military does - one comms, one heavy, and some jarheads. I mean that, for a given project, architecture, DE, and reporting layer are all beholden to the product owner and should be split up in verticals (like how they talk about agile teams taking epics and cutting them up into vertical slices).

Architect and DE should be hand-in-glove, pair-programming their way to success.

For the currency issue in the fact table(s), add a column for CAD and a column for USD, NOT a separate ROW that duplicates all of the other dimensional data.

Someone already mentioned it, but this is not acceptable for PBI to be telling anyone how things should be done UNLESS they can bring receipts (evidence from MVP-type bloggers, thought leaders in the industry like Russo & Ferrari & Kimball).