Yes these are good ideas. The inclusion of a deployment model has been in the plan from day one, but we haven't yet fleshed out how it should be used.
In terms of the simulation functionality, it sounds like it would be useful to have different 'implementation profiles' associated with a deployment model, representing (1) the alternative technologies that may be used, or (2) different performance information related to the various hardware/software/services involved.
It would also be good to capture realtime information from the production use of some of those components (whether servers, network, services, etc) and therefore enable the simulation to be based on realistic information.
Can you create some jiras for the different features - one per discrete requirement, with relevant links between them to show dependencies.