I do not ask you to respect that the processor is a physical black box whereas interpreter implementation is not that clear. As CS, you must look at the functionality aspect -- both processor (physical machine?) and interpreter (virtual machine?) execute a program (a stream of commands).Isn't to interpret the code just means to evaluate/to execute/to process it?There is a long article on interpretation in Wikipedia. It uses a lot of words to explain what is interpretation and it even says that it is execution of instruction stream. But nobody stood up and stated that it is just what the processor does (like the child in the Emperor new clothes)! Why should we think that these are two different things? Processors even invented JIT-compilation (called microcoding) earlier than virtual machines.Also, bytecode interpretation should give additional clue. It looks like machine code absolutely (to be executed by virtual machines). So, are interpreters just virtual processors? The self-checking questions are: What if vendor of your favorite processor discloses you a terrible secret that your instructions are not executed directly but converted into a true machine language beneath, before submitted to the real processor, is you language interpreted or machine? What if instruction stream for a real processor is executed by emulator (virtual machine) then is it executed by the processor or interpreted? Can the processor that executes an interpreted language (bytecode or script) is not a processor anymore but an interpreter? 
Can terms interpreter and processor be used interchangably?
terminology