Are IP Packets to Blame?

Yes, the parcial problem is that but the cause is not exactly because of the real-time protocol that is used to send and receive data from server to client and vice-versa, it's how they coded it in the game to manage those data.

For example, implementing a logic that takes SO LONG to finish will cause FPS drops and freezes in your game.

About the zombies part, for example they coded in the backend server to send the position of the zombies half of a second or even less, or they're sending useless information that wasn't needed and could be done in the client side, for example, the server just giving a new path to the zombie with a simple X Y to all clients(Killer and Survivors), and then in the client machine these paths calculation would be done.

This brings a interesting topic about DH on consoles or random freezings, people on console press the button to DH, the DH input is sent to the server and it does some validation, and then sends the response back, during this wait it will freeze the game because it is waiting the data to continue to execute what it was supposed to, but one thing is certain: It is frezing everytime you DH because it is executing some code that takes so much time to finish, because it is not well coded or because it is awaiting something which takes some time.

One of the issues that I believe cause my Xbox1 to choke & gag so badly with DBD is the fact that every element of every killer (perks, add-ons, power, sound, everything) is loaded into each and every trial, regardless of which killer it is.

So when something is needed, the ride down the spaghetti, rigatoni, and ziti might take a minute or three to find it. And four killers are added per year, lengthening it further.