https://prnt.sc/10vqo4l
https://prnt.sc/10vqpav
Assuming behavior changed by Space Exploration. If not fixable, SE should me marked as incompatible.
https://prnt.sc/10vqqsq

I just ran into the same problem when I installed SE on top of an existing save. Thankfully it's only happening with new chests.

This is a big bummer.

It looks like the problem is that SE has a LinkedContainer.on_entity_created handler that is looking for all "linked-container" entities. This is leveraged in the Teleportation technology.

They probably should fix on their end since other mods will likely use this same entity type going forward.

Please report to SE. There is nothing to fix (nothing wrong) on my end.

Regarding incompatibility marking, I think it is a serious move, and should be used cautiously. Buggy mods do not deserve such "severe penalty". Just let them know and give them time to fix.
Personally, I will only consider applying that for marking theme-clashing mods (if I ever make an overhaul mod...), mechanic-clashing mods (such as RSO, if I want to keep my own resource autoplace control), intentional trolling mods, or game-breaking mods (like if an overhaul mod removing vanilla entities).

I suggested that they fix in their discord. It's under consideration.