Actually, major compaction *does not* stop minor compactions. What happens is that due to the size of the size of the sstable that remains after your major compaction, it will never be compacted with the upcoming new sstables, and because of that, your read performance will go down until you run an other major compaction.
"2. Switch to Leveled compaction strategy.
- It is mentioned to help with deletes and disk space usage. Can someone confirm?"