We will not be fixing this issue. Please see below for a small explanation why:
Cursor.Current is a .NET API which returns the state of the cursor while over a Windows Forms application, not the cursor state in Windows / any other application. This is not the intended use of the API, and we cannot alter the .NET behavior. Also, as far as we’re aware, there isn’t any out-of-the box way to get the cursor state in .NET, but it can be done through some windows interop, see here: C# - How to get current cursor state (if its currently arrow,hand,waiting etc) - Stack Overflow
Given the above, it might be a good solution to leverage the Coded Workflows to produce a custom code snippet that will perform this task if possible.
Edit. In fact, a post over here might be helpful: