Is it okay to use a ‘HttpPut’ or ‘HttpPatch’ verb and allow the API method not to check for a Patch doc or resource?

I’m not sure what the correct procedure is, when you have a question based off an answer you read but it is a seperate question that arose because of the answer provided.

the answer in question Which HTTP verb should I use to trigger an action in a REST web service?

Walkthrough of my method, where this is relevant

[HtpPut("StartDate/{id}")] public async Task<IActionResult> StartDate(int id) {     //do checks to see if resource exists, and authorisation .     //start backend task     //if task successfully starts update 'isStarted' field for the entity with the inputted id     //return status code 200 if there is no errors  } 

Question when designing an API that adheres to REST as much as possible, is it okay practice in a situation like above to use a ‘HttpPut’ or ‘HttpPatch’ verb and allow the API method not to check for a Patch doc or resource? ie: the user sends a request, with whatever resource or patch doc they wish and the server does not care as long as the request id is valid and the user is authorized.

secondary question if this adheres to REST(or even if it deviates from REST), is what I am doing a good solution that is acceptable, or is there a cleaner design I should be implementing for a situation like this?