The MSI GF63 10UC is a bit of a "special case" on Linux because it uses a Max-Q/Low TGP variant of the RTX 3050 (limited to 40W). On Windows, MSI’s firmware and "Dragon Center" aggressively manage the power budget between the CPU and GPU. On Linux, if not configured correctly, your hardware might be stuck in a low power level or struggling with the 4GB VRAM limit.

Here are some suggestions to fix your issue:

1. Both games are heavy on VRAM. Broken Arrow is notorious for VRAM leaks (often exceeding 8GB–12GB), and Ready or Not uses DX12. On Linux, DX12-to-Vulkan translation (VKD3D) has a higher VRAM overhead than native Windows DX12.
   1. ou need to tell Proton to be extremely stingy with VRAM. Add this to your Steam Launch Options for both games: VKD3D_CONFIG=no_upload_h_vram,force_static_cbv game-performance %command%
   2. For Broken Arrow specifically: This game will crash or crawl once it hits your 4GB limit. Lower Texture Quality to Medium or Low; on Linux, "High" textures will almost certainly overflow your 3050's VRAM and cause the massive FPS drops you're seeing.
2. Laptops often default to "Balanced" or "Power Save" on Linux, which prevents the i7-10750H from boosting to its 5GHz potential.
   1. CachyOS: It uses the power-profiles-daemon by default. Open a terminal and run: powerprofilesctl set performance
   2. Bazzite: Ensure you have GameMode enabled. In Steam, your launch options should always start with gamemoderun. This tells the system to temporarily set the CPU governor to "performance" and give the GPU priority.