Whilst it is useful that the Exchange validates resources against the meta.profile and returns an OperationOutcome if they fail validation. There are use cases (especially in Sandpit), where it would be useful to instruct the Exchange not to perform validation for a specific request (e.g. via a custom header / parameter), and receive the 'unvalidated' response...
Development teams in Data Providers are unsure what the exact issue is, but are unable to share the JSON with a support team (e.g. Email exchange rejects any attachments with JSON content, or third party Developers are connecting to the trust via a VDI, which doesn’t allow them to copy and paste to their local pc / email)
Occasionally the Exchange incorrectly returns validation issues (see Jira log) ... which can act as a blocker to team that are developing solutions that need to send requests for the affected resources