How to fine tune a huge problematic Heap Table?
Based on those facts, 190M rows, 450GB, un-indexed heap, long-running queries, you should create a Clustered Columnstore index and store the data in compressed columnar format.
However, that might not be the optimal solution, as you still have a table with no key and no indexes, which is strange.