### ImageMagick version

7.1.1-33

### Operating system

Windows

### Operating system, version and so on

vs2017 v141 windows sdk 8.1

### Description

I examined the ModulateImage function in the enhance.c file, which has an OpenCL-accelerated version named AccelerateModulateImage. I found that the SetMagickResourceLimit(ThreadResource, limit_) setting does not appear to be effective for functions that support OpenCL acceleration. If OpenCL runs on the CPU, would it potentially utilize all CPU cores to their full capacity?

### Steps to Reproduce

none

### Images

_No response_
Does SetMagickResourceLimit(ThreadResource, limit_) impose restrictions on functions accelerated by OpenCL?
This is a GitHub Issue
repo:ImageMagick
owner:ImageMagick
Title : Does SetMagickResourceLimit(ThreadResource, limit_) impose restrictions on functions accelerated by OpenCL?
Issue date:

--- start body ---
### ImageMagick version

7.1.1-33

### Operating system

Windows

### Operating system, version and so on

vs2017 v141 windows sdk 8.1

### Description

I examined the ModulateImage function in the enhance.c file, which has an OpenCL-accelerated version named AccelerateModulateImage. I found that the SetMagickResourceLimit(ThreadResource, limit_) setting does not appear to be effective for functions that support OpenCL acceleration. If OpenCL runs on the CPU, would it potentially utilize all CPU cores to their full capacity?

### Steps to Reproduce

none

### Images

_No response_
--- end body ---
