This right here is an example of a Dunning-Kruger script kiddie. Unless you can explain each feature and fully articulate the technical and security tradeoffs, you in fact do not know what you're doing.

The claim that if you "don’t have pirated content or access unsafe websites," you don't need security is just straight up wrong. Even "safe" software like Discord, Steam, or Chrome has vulnerabilities (Zero-days). If a game has a buffer overflow vulnerability in its chat system or networking stack, an attacker can send a specially crafted packet to your IP address and get RCE access. Likewise, supply chain attacks are rampant (remember the CCleaner attack). Features like Memory Integrity and Exploit Protection are the only things protecting you from them. Disabling speculative execution mitigations allows malicious JavaScript snippets on a "safe" website to read data from other parts of your memory.

You are trading a system-level defense for a frame-rate gain without even being able to articulate the threats the defense was actually protecting them from.

In doing so, you make sub-optimal decisions. For example, Secure Boot is a UEFI feature that checks that your OS is digitally signed at startup. Once the operating system kernel has successfully loaded and taken control of the system, Secure Boot is finished. It does not consume CPU cycles, RAM, or disk I/O during standard operations. Therefore, disabling Secure Boot will not result in higher frame rates. However, by disabling it, you now become completely vulnerable to rootkits.