Query on creating a task for PATCH operation

Under AccountService there are many patchable properties such as,
LDAP properties/ActiveDirectory Properties
 - Authentication
 - LDAPService
 - ServiceAddresses
 - ServiceEnabled
 - RemoteRoleMapping

AccountService properties 
- AccountLockoutCounterResetAfter
- AccountLockoutCounterResetEnabled
- AccountLockoutDuration
- LocalAccountAuth
- ServiceEnabled

As per openapi.yml, redfish serivce can respond either 200 or 202 or 204 response for AccounrService PATCH operation.

In our current redfish implementation we are returning 200 as a response while giving PATCH call to AccountService URI.

We got in a situation wherein we are planning to create a task while PATCHing LDAP and AD properties by returning 202.

can redfish implementation return 2 response code(202 or 200) based on the request body?

i.e.,
If the patch request body has LDAP and ActiveDirectory properties then create a task and return 202 for as the http response.
and
If the patch request body has AccountService properties alone (like AccountLockoutCounterResetAfter,  LocalAccountAuth etc.), directly patch and return 200 without creating a task.

Please let us know your view on this case?