Improving INP with setTimeout: Optimization or Metric Hack?

I'm working on improving INP scores on my website. Some buttons trigger long tasks -  for example, opening a popup. I’m aware of techniques to break up and optimize these tasks. However, INP only measures long tasks that occur during user interactions.

Here’s the situation:
I have a button that opens a popup. The interaction time reported in Performance tab is around 150ms. While it's possible to optimize this, it would require significant effort and investigation. However, I’ve found a simple workaround that improves the reported INP score: wrapping the click handler logic in a `setTimeout`:

```js

// Before
btn.addEventListener('click', () => {
  showPopup();
});

// After
btn.addEventListener('click', () => {
  setTimeout(() => {
    showPopup();
  }, 0);
});

```

With this change, the interaction time is reported as very low because the long task is deferred and no longer attributed directly to the user interaction. Of course, the long task from `showPopup()` still runs - it just doesn’t impact the INP metric unless the user interacts again during its execution, which seems less likely.

My question is:
What are the practical implications of using this workaround?
Is there a good reason not to use this trick? It feels a bit off, since it doesn’t actually improve performance - just avoids the INP penalty.