High CPU Utilization When watch Command Is Idle

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Apple platform

macOS

### Framework version

Other

### Describe the bug

When the watch command is in an idle state (waiting for the next execution interval), it consumes an unexpectedly high amount of CPU resources. This occurs even when no active processing should be taking place.

### Expected Behavior

CPU usage should remain minimal—ideally close to 0%—while the command is idle and waiting between executions.

### Steps To Reproduce

Run watch command and see the CPU use.

### Exceptions (if any)

_No response_

### .NET Version info

_No response_

### Anything else?

_No response_