What you may what to change if you are only playing around is to change the capture mode to ALL. This can have detrimental effcet on a system witn lot of unparameterised queries. Then again, this was the default setting in SQL 2016 and 2017.
The other two may not have as much effect as you think, because when you query store views, they take data both from what is on disk and what is buffered in memory. The effect of the flush parameter is how much you lose in case of a crash or a failover.
ï also like to point that when we recommend you to stick to the defaults, we have a production scenario in mind.
I'm afraid that I did not watch the video.