I don't have energy to discuss your statements in detail, but OK, I'll give you a brief response.
OData not supported SOAP.
This makes no sense. OData and SOAP are two distinct ways to create web services; you can't say that one support or doesn't support the other.
Custom service - Supported both SOAP and JSON.
The original sentence you're trying to rephrase was "Custom services have two endpoints: SOAP and JSON-based". You almost managed to understand it, but the JSON-based service endpoint isn't the same thing as JSON. JSON is just a data format.
OData services are mostly used for CRUD operations.
Yes, but that's not the case of OData actions. You can write any arbitrary code in the action.
Custom services are used when like to get data back.
That's incorrect. You can use both OData actions and custom services not just to get data back, but also to send data to F&O or to trigger an action. It was discussed in my last reply.
OData and Custom services both are supported Synchronous integration. As both are return result immediately.
Calling an endpoint is a synchronous action indeed. Just note that the call may come from an asynchronous process (e.g. scheduled flow) and start an asynchronous process (e.g. a batch).
