I'm not aware of any such comprehensive resources, unfortunately. Mainly, because all of the different solutions put together, make for the better part of a game engine, so where all the pieces exist together, they will make up an engine (Source or Unreal or whatever.)
And, the few resources that exist for game engines, typically do not put networking as their main illustration, because networking is only used by a subset of games, AND it's pretty complex (as you are finding!)

The meta-advice I can give is to separate concerns between different pieces of code. In Object Oriented code, this should be trying to achieve the "single responsibility principle." In a more functional approach, keeping each function shorter/smaller, and composing functions to achieve the end goal, would achieve the same results.

Yeah, networking for sure is something that you can't really build to be as general as graphics or collision (which most engines make their staple). For graphics if you want to make a completely different look it usually comes down to shaders (in the code portion at least) whereas networking there's lockstep vs predicted vs rollback and others...so I guess I shouldn't be too disappointed!

For your second paragraph, Good advice! When I look at other engines like Source they seem to always have command line tools to disable entity interpolation, prediction and so on, so in theory it seems all those components are just layers over the core logic of the world. I've rebuilt my game 4 times now (although bear in mind I had zero networking experience at the start), and I've written some stuff down describing how I want to do it this time, which I think I'll post here to see if anyone else is interested in the topic.

I previously tried to find the same thing, then I realised that the task is simply too big - or game specific - that it's simply not there, at least not yet. Some tutorials exists in youtube for making MOGs, but I don't even bother seeking those out as they are not really worth of your time. I think a lot of people decides that it's time to make tutorial named "How to make MOG" once they know how to pass values between client/server using simple "x/y" values or inputs - which is fine. But what they doesn't say is the fact that it doesn't work anywhere else than localhost because problems caused by latency is not solved.

Nevertheless, I have been lately reading articles from: ithare.com and gafferongames.com.

Hence, you can find more articles (around 40 - 50) from digital libraries like ACM and IEEE if you use keywords like "multiplayer online game architecture" etc. However, most of these articles needs to be purchased and you can find more in-depth knowledge using resources already listed above.

Great links! For anyone reading this in the future, start at the beginning of the ithare stuff and go through it. It seems dense and low leveled but already is really useful. Only skimmed the gaffer stuff, and while it's less structured looks well written.

Have a look at my collection of links at http://www.gamedevpensieve.com/network. One of them might give you some insight :).

Lots of good variety here, especially in topics that aren't common to see discussed.

Given that it doesn't seem likely there will pop up a tutorial titled "How to create a sword boomerang game in 5 easy steps," I'm going to start working on create a robust system for my above specs, and I'll post some high level designs here when I've got them. In theory, it should mostly come down to sending data to be synced and handling certain state changes as events (if a player enters the jump state, play appropriate animations). Then for all the smoothing and prediction and whatnot should all be done as a layer on top of this.

Yeah, the Overwatch video is great, was good to see that some of the things I was doing (predicted projectiles) were on the right course.

As we finally arrived at the weekend, I managed to sit down and write out a rough draft of how the networking should work. I outlined the server and client loops, as well as the base NetworkObject class that all networked objects would inherit from.

- Will need to keep track of the server's tick number on the client to be able to accurately reconcile objects

I'm sure I'll discover that some of this won't work quite so simply once I start implementing it, but I think it's a good star to steer my ship towards.