How does API Rate Limit classified?

I have 2 processes running (shown in below table):

+--------+-----------------------+--------+------------+
| Method | Endpoint              | Weight | Process ID |
+--------+-----------------------+--------+------------+
| GET    | /fapi/v1/order        | 1      | 1          |
| POST   | /fapi/v1/order        | 1      | 1          |
| POST   | /fapi/v1/order        | 1      | 1          |
| POST   | /fapi/v1/order        | 1      | 1          |
+--------+-----------------------+--------+------------+
| GET    | /fapi/v2/positionRisk | 5      | 2          |
| POST   | /fapi/v1/order        | 1      | 2          |
| DELETE | /fapi/v1/allOpenOrders| 1      | 2          |
| GET    | /fapi/v2/balance      | 5      | 2          |
| POST   | /fapi/v1/order        | 1      | 2          |
+--------+-----------------------+--------+------------+

In any time between the interval of 10 seconds those 2 processes might run together.

How much is the weight my processes contribute to the API rateLimit? And which API rateLimitType is it weighted to, “REQUEST_WEIGHT” or to the “ORDERS”?

Because in the documentation, the list of endpoints only have weight information but not the classification of each endpoint.

Thank you.

For rateLimitType - “ORDERS”, this will apply to endpoints that are placing orders. For fapi, you can place 300 orders per 10 seconds. This is calculated based on account.
For rateLimitType - “REQUEST_WEIGHT”, all endpoints have to obey this limit. For fapi, you cannot exceed the request weight of 2400 per minute. This is calculated based on IP address.

Thanks for your response.
So in other words, any “POST” request made to endpoint “/fapi/v1/order” will contribute to both “REQUEST_WEIGHT” and “ORDERS”.
While the rest only contribute to “REQUEST_WEIGHT” only.

That is correct.

Thank you very much @Chai
I wish I could upvote your answer.