jemikwa

Robit, mimicking how Zoidberg calls Bender sometimes

Short answer, likely yes. It's not definitive, you could still slip by after sending enough mail, but you are also very likely to get whacked because that VPS IP doesn't have an email sending reputation.

Longer answer, email gateways like Google, Microsoft, and Proofpoint don't really care who owns what IP. Well, they might, but they're more concerned about the sending habits of an IP. While you might send good mail from that IP, there's no reputation for it, so you could be whacked for having a neutral reputation (the ol' credit score dilemma but for email).
In order to have a good reputation, you have to send a large volume of messages very gradually over several weeks to "warm" your IP as a reputable sender. I went over this slightly more in detail in another reply, but this article is pretty concise on how an enterprise accomplishes this with a dedicated IP at a provider like SendGrid: https://docs.sendgrid.com/ui/sending-email/warming-up-an-ip-address

It's about sample size. Mail gateways won't designate an IP as a reputable sending IP until it assesses a large volume of mail sent over a long period of time. You can't send the quantity it wants all at once or even in a short window because then you'll be designated as a spammer. So you start small with a few a day and gradually ramp up sending over multiple weeks or months to eventually send several thousands of messages in that period.

Spammers and malicious actors too often spin up new IPs for sending mail, so gateway patterns already implicitly mandate that email should come from IPs it's already judged reputable.

You as an individual can't reasonably warm your own IP. This is why services like Amazon SES or Sendgrid exist because they have huge IP pools that are ready to go. Plus, those services are very concerned with reputation and have bounce/complaint metrics defined to warn customers that abuse or poorly configure their sending habits.

This next example is what I'm most familiar with, but I'm sure there are other services like this. If you're a big enterprise and want your own dedicated sending IP because you're concerned about using a shared pool, you could use something like Amazon Pinpoint which allocate IPs for your org to use in SES, but they have to be warmed before you switch your production workloads over to it full-time. It automates some of the gradual-ness of warming so you use a mix of SES plus your Pinpoint IPs to keep mail flowing for your product.

It looks like Sendgrid also does dedicated IP warming guard rails too. This article is pretty decent for understanding how it works - https://docs.sendgrid.com/ui/sending-email/warming-up-an-ip-address The per-day warming limits give you an idea of what scale this kind of process is used for.

Ohno

Definitely listen to this. IP Warming is a very real problem and you have to send thousands of messages at a very gradual rate for most email gateways to 1) mark you as a proper email sender, and 2) classify you as a reputable one that isn't sending spam. Using a public/private cloud IP isn't enough, it should be a service already used for mail sending.

If you self host sending email and ignore using a service for outbound, make sure it isn't at home. ISPs often block SMTP traffic to keep people from spamming others from their home. A lot of IP blocklists also auto block home IPs so you may not ever get your messages delivered.

Make sure to set up SPF/DKIM/DMARC. At the very least SPF, DKIM if the platform supports it, and ideally all three or SPF+DMARC. It's not that hard to configure if you do it as you go instead of years down the line after you have a dozen services sending mail as your domain.

I use the Outlook app for separating entities before I learned that work profiles were a thing and that my company has them turned on. Gives me different notifications I can control instead of all through Gmail, it's still sandboxed because O365 does the same containerization, and it also does calendar syncing.
My only complaints are it doesn't handle password changes very well (have to completely re add my profile when it's time), and it is Outlook focused so it misses some Gmail features. This also doesn't solve your Google Meet problem, but at least it's two out of the three.

ONCE AND FOR ALL

We added a tilt sensor to our door that shows the state of the door for the most part. The threshold we have it at doesn't detect if it's partly open, but that's okay for us because we never leave it cracked

Our solution that we set up years ago was to connect a Shelly to circuits on a normal, dumb door opener. The Shelly triggers open/closed itself and since the signal comes from the opener, there's no crypto nonsense to figure out. It always works, no matter what MyQ/Chamberlain/LiftMaster do. Bonus, it also works if you have a very old opener.
We also supplemented this with a tilt sensor so we know the state of the garage door. The door can still be cracked and not registered as opened, but that's a compromise we're okay with since we never leave it intentionally cracked.

Yeah you'd need an L7 application layer filtering firewall to catch DoH since it would detect the SSL packet signature on port 53. Unfortunately that balloons the cost of the device past a reasonable level for a home aficionado.
A workaround for now would be to block known public servers that use DoH like Google DNS, since a lot of devices are adding features to enable DoH by default at the OS level

Shellys are amazing. We use the pucks everywhere for anything that's not innately smart.

Some of our use cases:

• Kitchen cabinet lighting that syncs each strip with each other as well as the overhead lights. Or the cabinet lights can be turned on independently.
• Garage door opener, because MyQ sucks (it's hooked up to a real physical garage opener button and triggers the button for us)
• Outlet power monitoring (mostly for fun)
• Can be put in light switch boxes in lieu of something like Kasa switches, but the physical switch won't follow the light state any more. Similarly, smart wall outlets for power toggling

The good news is, based on the diagram looking like it's straight from AWS docs, there's a Cloud formation template for all that.
Bad news, good luck troubleshooting any of it if something breaks