Is DevOps methodologically anyhow different or even applicable in the academia field if used in research and science projects?
Disclosure - I have not worked in proper ("Academia") research and science projects.
DevOps should be just fine for researchers. As in the commercial world, the interesting bit will be to pick the line where the DevOps teams start and where the lower level base ops begins. This is not a contradiction. You may still have a dedicated ops team which provides the hardware, networking, OS, container management (Kubernetes ect. if you have something like this) and so on.
The most crucial part is that these ops guys now provide the base for the other teams. This means there is not a hand-over of software between the other teams and ops. Ops has the responsibility to provide the DevOps teams with an infrastructure (or platform, whatever you may call it in your case) so they can do their slightly higher-level stuff in a self-sufficient manner. The base ops team would do the hard lifting (i.e., IAM, license stuff, security issues etc.).
There is a plethora of possible ways to structure this. E.g., if you are in a non-techy research field (say, statistics, where people know
R but nothing much else), you will have a different structure than if your researchers are hardcore coders/OS experts (say, the VR department where researchers program GPUs etc.).