Serious question, Slav Power senpai: how would you suggest a clueless outsider to Windows' CLI to learn it?
Interact with a command line. Be it in DOSBox, cmd.exe, PowerShell, get the grasp of the basics. How to list a directory, how to navigate back and forth, how to execute software and pass parameters to it, what's a relative and what's an absolute path, what the PATH environment variable does, what a script file does and so on. Eventually you'll find parallels between MS-DOS, Windows and Linux with some obvious differences like how under MS-DOS/Windows it's "dir" and under Linux it's "ls".
Though, the thing about it all is that you need that mindset of a nerd. That this is something that intrigues you and you want to learn it just because. Learning the command line can help you a ton when you realize a lot of the GUI stuff has a lot in common, like LNK shortcuts and how you can pass parameters within them, or how when you set up a path to something it can be relative and how you can use it to your advantage, or how you can add some directory to the PATH variable so that you don't need to invoke the full path to run some program and so on.
Or how you can use scripts to automate certain tasks. For this I highly recommend learning PowerShell, and if you like committing sacrilege, PowerShell 7 is also available for Linux. Think of it as programming lite, where most of the hard work of making software that does this or that is already done and you're left with a documentation of what each command does. Then it's up to you to map out the scheme of what you want to do step-by-step and write it out in a script to automate it for you. Programming isn't like learning a language, but rather learning a syntax that goes from top to bottom that does exactly what it's told to do. Scripting languages like PowerShell or AutoHotkey are a good way to get a grasp of it while being able to quickly make something that's useful to you.
If you need another incentive to try and learn something like this, then trying to run an old game in DOSBox is a good starting point for example. You'll have to interact with a command line to get things running and a lot of it will be transferrable to Windows due to obvious reasons. The end goal of any command line learning is you learning how an operating system works from the practical side of things. What a program is, how it works, how you can influence the way the programs work, the funamentals of paths, variables and so on. All of computing and software is a flowchart, and your goal is to train your brain to see those flowcharts.
).
