Hope it is Always on setup, any Database to read it has to be in Synchronising mode or Standby mode in log shipping. If it is suspended, the DB is...

is the above comments was the solution? what is the difference is execution plan post changes?

how about policies and access for your login/group. any error in Windows error log which you can post.

Do we have any other files in .....Setup Bootstrap\Log\20220802_031252\ folder?

Are you administrator in the server ? and check if the disk is compressed.

Adding to above point , as it is C drive check if Antivirus or any other tools holds the file for SQL not to be able to access.

Try SQL service...

try undocumented SP, for each individual DB query

EXEC sp_MSforeachdb @command

Note: Set full recovery plus full DB backup to secondary servers also necessary.

This seems to be appear since older versions, i dont think any solution available as far as i know.

Move the page file to separate drive as a best practice to avoid the IO on System drive, some put that in a SSD to have better  performance.

What is the db compability level

There is no such direct recommendation for CPU utilization but you can check the performance using a monitoring tool, PerfMon or other SQL monitoring tools.

What is the RAM...

Mostly the DR or secondary servers will be of lower configuration as that of Primary. but based on your usage like reporting etc you can have almost of same configuration.