I think you're still right, though: the larger picture these things will slot into is as subsidiaries for what IBM has termed "cloudlets": automatic device-launched containers, operating on ISP commodity-IaaS clouds (i.e. at the "edge" in the same city the user is in, where all the CDNs and caches and mirrors they access already are.)
Cloud services would probably be written with cloudlet service-worker containers in mind, and then the home-server hardware would just be a latency-optimization, "stealing" workloads from your cloudlet to your LAN when all the traffic is just going to be over your LAN (e.g. for a home streaming service like Plex, or a game server at a LAN party) and then moving them back if you try to speak to the cloudlet from outside your LAN.
Cloudlets are the more important part of that vision, but I could see the home-server part of the design coming first, just because so many companies seem interested in putting devices into home networks that could run them (e.g. the Apple TV and its class of products; the Amazon Echo, Google Home, and other "voice boxes"; most "smart home" device hubs.)
That, or the "home server" component will be a separate mode / augmentation for what are still primarily cloud-based services.
I'd much rather locate my personal server (or VM) in a real datacenter and behind a better SLA than my flaky Comcast.