(Written) Languages are nothing more than structured sequences of symbols which contain information. That is no different to what you have. Files of data, files of configuration settings are all sequences of symbols that contain information. The ordering and sequencing of the symbols needs to be recognised in order to discover (or match) the information contained therein.
However, there are different ways of structuring the symbols to represent information. Some ways of organising the symbols are easier to recognise than others. By easier I mean with less code, less time, simpler algorithms. Some are more difficult.
What you are asking really translates to, "does this example arrangement of symbols require an algorithm of this complexity to be recognised?"
The answer is straightforward Computer Science. I'd just use the Chomsky Hierarchy to evaluate the type of algorithm needed to parse (match) the symbol sequences in the file.
Without further detailed explanation, it is sufficient to say that the language is either type 2 or type 3, and can certainly be parsed by an LALR-parser. The only remaining question left to be resolved, is whether a LALR-parser is too complex for this language.
Can a regular grammar (and hence regular expressions) we utilised for this task? Your example of the file structure is actually insufficient to answer this question. You need to know if the structures can be nested or not. Can a BLOCK contain a BLOCK or not?
If there is no nesting, the regular expressions are sufficiently powerful, and there are plenty of tools that do the job (like egrep, perl, awk, sed, findstr).