Is it safe to delete logs-deprecation indices, where can we disable creation of these indices?

We have some system indices generated by ES, can we turn off generation of these indices and is it safe to delete them?

health status index
green open .ds-ilm-history-5-2023.06.02-000012
green open .ds-.logs-deprecation.elasticsearch-default-2023.08.01-000017
green open .ds-.logs-deprecation.elasticsearch-default-2023.07.02-000015
green open .ds-ilm-history-5-2023.07.02-000014
green open .ds-ilm-history-5-2023.08.01-000016

It seems these indices can't be deleted even when Ilm is stopped:

{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"index [.ds-ilm-history-5-2023.08.01-000016] is the write index for data stream [ilm-history-5] and cannot be deleted"}],"type":"illegal_argument_exception","reason":"index [.ds-ilm-history-5-2023.08.01-000016] is the write index for data stream [ilm-history-5] and cannot be deleted"},"status":400}%

{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"index [.ds-.logs-deprecation.elasticsearch-default-2023.08.01-000017] is the write index for data stream [.logs-deprecation.elasticsearch-default] and cannot be deleted"}],"type":"illegal_argument_exception","reason":"index [.ds-.logs-deprecation.elasticsearch-default-2023.08.01-000017] is the write index for data stream [.logs-deprecation.elasticsearch-default] and cannot be deleted"},"status":400}%

Maybe someone can point me to the right documentation. Currently I can't delete last index of a data stream whether ILM is turned on or off.

"You cannot delete the current write index of a data stream. To delete the index, you must roll over the data stream so a new write index is created. You can then use the delete index API to delete the previous write index."

Also I can't increase the replication factor on these indices, cluster acknowledges the change but replication factor stays at 1, creating fake "RED" status conditions.