Client(s) disconnected due to invincibility (Smokescreen + Dojo)

SCENARIO 1:
A Shadower used max-level Smokescreen for the entire party, and a Buccaneer used Time Leap to refresh the cooldown of Smokescreen. The moment the 1st Smokescreen disappeared, the Shadower immediately used his 2nd Smokescreen. If timed well and the party remained in both Smokescreens, they will all disconnect (including the Shadower) around the timeframe that the 2nd Smokescreen disappears. Keep in mind that Smokescreen lasts for 90 seconds, so both well-timed Smokescreens would give the entire party a total of around 3 minutes of invincibility.

Some points to note in this scenario:
A. Only those that in the same party of the Smokescreen that remained entirely in both smokescreens will disconnect.
B. This "invincibility check" seems to also apply to i-frame of skills that make the character untargetable such as Buccaneer's Demolition, since my party's Buccaneer disconnected before the 2nd Smokescreen disappeared in one run that I was in (as a Shadower), in addition to me already making sure to wait for a few seconds before popping my 2nd Smokescreen. The rest of the party did not disconnect.
C. I'm uncertain if Shadow Shifter would play the same role as point B or count similarly to that of a MISS hit.

Following point B, the workaround for this would be having your party take any type of damage (not sure if MISSES or a Shadow Shifter's proc also count) before re-entering Smokescreen. In other words, if you took any damage between the two Smokescreens by either having the Shadower pausing in-between, or exit the Smokescreen by walking out of it or leaving the party, you will not disconnect.

It also appears that different Smokescreens from different Shadowers do not trigger as often due to two different client syncing/connection (needs to re-check).

---
SCENARIO 2:
As an Ice/Lightning Mage: I was doing Dojo, and had used the Invincibility Combo ( < + Ctrl + Alt ). I looted the Protective Shield (the bubble item) around the time Invincibility skill disappeared, which also granted longer invincibility. While staying under the hitbox of the boss to make sure I don't attack the spawned minions (i.e. I was killing Lord Pirate with magic claw), I disconnected some time later while still having the Protective Shield active.

Some points to note in this scenario:
A. Both invincibility appears to be the same visually as well as type — they both convert all hits to MISSES.
B. Despite the Protective Shield stating that it will only protect you from up to 3 attacks during its duration, it actually protects you throughout the entire duration, which lasts for 1 minute.
C. The Invincibility skill lasts for 30 seconds.
D. It was a Mage, so it has very low avoidability.
E. Due to the character staying under the boss's hitbox, the MISSES triggering in this scenario is at its fastest trigger time, meaning another MISS instantly occurs the moment the character's i-frame from previous hit is over.

Following the points above, I do not remember looting more than one (or two) Protective Shields, but even then, the invincibility would only add up to 2 minutes and 30 seconds (2 Shields + 1 Invincibility Skill). I suspect there's also a different "invincibility check" where if a character that has such low avoidability (e.g. Mage or Warrior) received MISS attacks too often, it would trigger the disconnection.

---
The disconnection for both SCENARIOS would put the affected clients back to the Login Screen with the message, "You have been disconnected from the server. Please try again later."

Grouping both since I assume their disconnect reasons are the same (due to Invincibility/Godmode check). It's likely replicable though tend to occur more unexpectedly during boss runs like Zakum (especially with Shadower + Buccaneer scenario above). I'm not sure what the timer of the check is, but based on SCENARIO 1 the invincibility check and disconnection seems to trigger around 3 minutes, but SCENARIO 2 seems to be a different check based on the amount of MISSES.

One other thread has also been made >>HERE<<, with case the same as SCENARIO 1.