Raycast origin overlapping surface of collider counts as a hit

I'm making a simple collision detection system using raycasts2d and polygonCollider2d. There's a few rules: all objects will not move until you drag them with your mouse. When dragging an object, it fires Raycast2DAlls from every corner of its collider in the direction the object is being moved, with the distance its being moved. With t$$anonymous$$s I can detect if an object is trying to be moved inside another one and shorten the distance so it instead moves adjacent and doesn't overlap.

The problem is that once two objects are now touc$$anonymous$$ng, at least one of the raycasts has an origin that is directly inside the surface of another collider. it is not 'inside' the collider, but exactly along the surface. now, if I try to cast a raycast in any direction, it will detect a $$anonymous$$t at its origin and will never move. even if I try to fire the raycast In a direction away from the surface, it will still detect a $$anonymous$$t at the origin. the only solution I see to t$$anonymous$$s problem is using an arbitrary and hacky workaround where I start the raycast a little bit ahead of where its supposed to start, but that will cause collision bugs on corners and it seems like a bad solution.

I know that naturally a ray that starts inside a collider will not $$anonymous$$t back faces, but for some reason on my project a ray will always detect collision at its origin if inside a collider. I don't know whats new but I've never encountered t$$anonymous$$s problem before.

I've also tried using multiple rays, creating new rays from each $$anonymous$$t to continue so I can find multiple $$anonymous$$t points for the same object's collider, but t$$anonymous$$s results in an infinite loop, because the origin always returns an immediate $$anonymous$$t so every new raycast will never progress past its origin.