try a lot I am afraid to damage my system.

Don't worry - it's safe here. Programmers make typos all the time.

the interpreter exists

For example, a file named thefile contains the following:

#!/bin/cat
blabla

Then, when the file has executable permission bit set, then executing the file itself will execute the program /bin/cat with one argument ./thefile, as if you would type /bin/cat ./thefile in your shell. Program cat just prints the content of the file, so when exeucting ./thefile will execute /bin/cat ./thefile with will print the file content to the screen.

$ ./thefile 
#!/bin/cat
blabla

the interpreter is not available

What happens if the interpreter specified after #! is not available?

If the shebang happens to be interpreted by your shell, it would be expected that your shell will then print some kind of an information message that it can't find the interpreter, with some error description that "this file does not exist" or similar. If the file is run via one of exec*() system calls, then the kernel will return with ENOEXEC error code (per source code here)

Let's take a file named anotherfile with the following content:

#!fdsafdsafafdasfdas
blabla

For example, Bash shell will try to parse #! line by itself. Bash interactive shell would print:

$ ./anotherfile 
bash: ./anotherfile: fdsafdsafafdasfdas: bad interpreter: No such file or directory

But, for example, Busybox's Ash shell presents a different message:

$ ./anotherfile 
/bin/sh: ./anotherfile: not found

Also https://en.wikipedia.org/wiki/Shebang_(Unix) might be interesting.