Blizzard has really inadequate wording for a lot of things…
So, all of those account bans are either stated as such (unless there is a specific error in the error messaging, which could be based on what original Diablo 2 was installed, and maybe re-patched) or they are unlisted, direct TempRealmDown or you will have a character selection screen blocked out on Battle.net.
Say I use the scroll wheel on battle.net. I will “Dropped due to timeout” message the game I’m in, not connect to any lobby chat, and try to auto-connect to Battle.net. Then it will say I cannot connect and must wait a few minutes. These don’t usually last more than 2 hours, but they are in the type of TempRealmDown that can last weeks, and the auto-timer can be altered.
“More than 8 clients” or “Business IP” I believe relate to an unknown IP being used and/or a machine’s unique ID being banned. These may not go away except to kind of filter out PC farms from normal users that got unlucky. This generally cannot affect a normal person unless there’s a cache or ISP issue (which is probably how/why you end up having it happen outside of multiple machines, an intentional configuration causes it).
“Hacked” (edited) DLLs or patches equate to an error that can be related to bug abuse or altering game content. This is a temp ban directly, rather than a machine block or IP block, because there is nothing to stop someone from keeping what they gain from it aside from bans and deletion, and they can break other things in the game sometimes.
Repeat connect/area is detected by the server as something that causes latency or server data errors, I think… Same with AOE spellspam. It might be remnants from a very old version of Diablo 2 and was to save machines mostly; they could probably remove that from the netcode - and they won’t because that’s extra work - but it probably was left since it has overlaps with the way the game engine can fail and allow duping/other bugs.
Zero Blizzard Representatives have logged into Diablo 2 since maybe 2008. I’m sure I’d be argued at over it but I’m not counting once every 2 years or every 4.5 when the game gets a patch/reset. They used to be there every day, up to 2008 or so. All chat-related bans must go thru at least a “Warden” or filter, and if someone is actively watching that, it’ll look like the Matrix and not an in-game thing, which can also be automated. Unless it’s an insane moment occurring on the Battle.net chats outside of a game, there are no temps going out for harassment or anything. It has to be related to advertisement of illicit content (game or not) if anything.
I’m not sure third-party programs can be policed properly because of Windows security settings being altered over the years and the game’s detection requirements not being met. They used to scan memory to bypass security issues within their client and got sued.
One other thing is that they don’t have the same patch validation as the past, and they now have to change it with certain Windows updates coming out and breaking some form of file/security rules. I believe in the past, especially with older versions of the game, they would add to/edit your files so waiting actually mattered with a lot of these things.
Long story shortened: All of their reasons are “correct” on code, but incorrect on reason and application; all of it is outdated and nothing like that happens pretty much. You did not do any of that unless you didn’t clean your computer out of some stuff that was altered (very likely with Windows 10, due to how old games are used most of the time).