React-dnd: HTML5Backend stops dragging when there elements in the DOM that appears/disappear in the drag event: CHROME

I've found a workaround, reading a lot, for this issue, setting a timeout and a state variable that I pass through components, I don't like it very much, because in these simple cases its easy to do, but in complex cases I should use context or something similar to make everything work.
https://codesandbox.io/s/react-dnd-sortable-holes-vxeus

I hope that you can guide me through a better solution, I would like to use the isDragging from the library instead of this workaround.

Our team have improved the state workaround creating a custom hook for the drag and drop provider, in any case that any of you face this problem, here is a solution while the bug is solved.

https://codesandbox.io/s/react-dnd-sortable-gaps-custom-9tl13

The main part consist on define a Context and a Provider to store the dragging status.

const DndContext = React.createContext([{}, () => {}]);

const DndCustomProvider = props => {
  const [state, setState] = useState({ dragging: false });

  return (
    <DndProvider backend={props.backend}>
      <DndContext.Provider value={[state, setState]}>
        {props.children}
      </DndContext.Provider>
    </DndProvider>
  );
};

Secondly, using setTimeout in drag begin function the end dispatched is avoided.

  const [context, setContext] = useContext(DndContext);

  const [collected, dragRef] = useDrag({
    ...,
    begin: monitor => {
      setTimeout(() => {
        setContext(() => ({ dragging: true }));
      }, 0);

      if (begin) {
        begin(monitor);
      }
    },
    end: (item, monitor) => {
      setContext(() => ({ dragging: false }));

      if (end) {
        end(item, monitor);
      }
    },
    ...
  });

  return [
    {
      ...collected,
      isDragging: context.dragging
    },
    dragRef
  ];

And finally, isDragging collected value is overwritten with the context value.

Does anyone have a solution or an idea for a patch for this issue that doesn't involve such a workaround?