History cleanup gone wrong - DBM Manually deleted hi_ data

Greetings!

As you read above, our dear DBM manually deleted some hi_ data while trying to do their maintenance.
I am well aware and had been using for a long time history cleanup processes, TTL configurations and periodically cleaning our unwanted history data. But what is done, is done.

Now I have a problem with our act_ge_bytearray, which has some historic data that can’t be cleaned by any means except manually - from what I’ve researched.

I’ve come across this answer in a similar post where golup567 mentions that the value of column “type_” as 3 means historic data.
From what I understand, deleting it shouldn’t affect the engine or run time instances and processes in anyway.

Can someone confirm his affirmation and my assumption?