Of course, if you don't set the public MX to google, blackberry phones won't use the right SMTP for outgoing mail, and then mail will fail DMARC, because you can't actually configure the SMTP server anyway. Hope they fixed that in BB10, before they stopped selling phones.
That is a) a very odd and theoretical setup b) probably would cause Google's MX to reject most messages for SPF failures
a) have your own MX that handles support mail and forwards employee mail to Google MX; G Suite provides a not exactly public domain you can forward to and you can whitelist your forwarder(s) IPs so Google uses the received headers for spam checking and SPF checks. If you don't setup the whitelist properly, a lot of mail will bounce or get flagged, yeah; but Google isn't dumb, they detect mail forwarding IPs with good behavior and will eventually semi-whitelist them without intervention.
b) The opposite way, where google is public MX and then delivers either specific addresses or unhandled wildcards to your MX to manage the support queue. (Or you might also forward it to a third party).
c) some people use third party email archival services (for example, ProofPoint) or virus scanning that shows as the public MX, and then forwards to some other MX for actual delivery
Nope, I use https://mxguarddog.com/ for one of my domains. That acts as a spam filter, but also hides the ultimate MX host.
Possible to find out using dig but not as simple as avoiding gmail addresses.