Why are mainServiceTax and mainExpenseTax ignored in my PUT and POST requests?

When a PUT or POST request to the /client or /project endpoint adds, changes, or removes a tax rate in the serviceTaxes or expenseTaxes nested object (objectState 0, 2, or 3), CORE ignores the mainServiceTax and mainExpenseTax values in that request. The serviceTaxes and expenseTaxes lists take priority over both fields, even if only one list changes. Items with objectState = 1 (unchanged), as returned by GET, do not count as changes, and an item sent without objectState counts as an addition. The mainServiceTax and mainExpenseTax properties are deprecated, so use serviceTaxes and expenseTaxes to assign tax rates from the Tax Rates catalog.