While formatting is a matter of preference, you shouldn't stray too far away from common ground. Consider moving your opening and closing brackets back, so:
Make a stand, either CamelCase or snake_case, not some weird offspring.
FYI - I'm a bit rusty with PHP and not a PHP expert in anyways.
Be strict on coding style and standard.
Clean the class responsibility, implement (at least) Single Responsibility Principle.
Make smaller functions.
Write Unit test.
This generated a lot of errors that was not there before.
This code looks okay, though has quite a bit of room for improvement - see this suggestions below. I like how the short array syntax is used in many places, as well as type hinting of parameters and return types for methods.
Some methods are a bit lengthy and a bit of an eyesore - e.g. the method EvaluateVariable- its more than 100 lines of ...
private function AnalysisVariable(string $varname, $var, array $indents): string
So there are a couple problems here. In the text of your question, you refer to this as AnalVariable. That's a particularly bad name as anal is an English word that is somewhat off-color. Fortunately changed here.
PSR-1 says that method names should be ...