Regarding inbox deliverability from dynamic IPs (like you'd have with a residential connection), it might work sometimes for short messages with no attachments to people you've corresponded with before, but I wouldn't expect general deliverability to be very good. You have the same problem with botnet infections / malware-based spam here as well; home PCs are much more likely to get infected with that kind of stuff (though WordPress exploits are VERY common on servers), so many people running mail servers will just straight up block dynamic IPs from big ISPs and assume that nothing of value was lost. Personally, for low-volume mail such as what a home server might send regarding maintenance or alerts, I'd recommend using a service like mailgun and hooking up to that with SMTP. It's a lot easier than running your own mail server, you won't have to deal with inbound spam if you're only sending, it works well with minimal setup, they guide you through each step, etc etc.
I run an email server with ten domains on it. Hotmail blocked me once, but I had no problem getting that lifted. No other issues for over five years now.
I have more of a problem with mail going the other way. I use a number of online spam traps to avoid spam, and my gf's Yahoo account often gets bounced by them.
Specific Yahoo servers regularly get flagged for spam, and if you're using a Yahoo account your mail will be filtered by many, many servers if it's sent from one of those IPs.
Those were the days that I don't miss.
I do have some mailing lists running from it, so it's possible it helped me that their users are making sure mails from it doesn't end up in junk folder.
Anyway, I would encourage anyone to run their own mail server, to prevent large provider doing what you're mentioning. Google already did this with XMPP. They made GTalk interconnected with rest of XMPP server, but as soon as they got a large base they disconnected from the rest and made their own proprietary network.