Congratuations on the journal, that must make you lots of friends (in academia), but of course also bring with it the work load and screen time. I share a similar interest in such workflows but there are definitely lots of things that could go wrong with them. There is some discussion of this sort of thing in this forum but comparatively little that is very advanced or detailed, presumably because of the inevitable problems and lack of widespread interest in this sort of thing.
Firstly, such devices clearly aren't designed for such a workflow and there is always quite a bit of resistance to better adapting them to it. The main problems arise from using eink in real time interaction. The screen refresh rates are low so the screen updates slowly. If you want to use VNC software to use it as a second monitor for another device, this adds even more lag. This particularly makes using something like a mouse difficult which can make conventional office software workflows difficult, although I presume something like Word can be driven from a keyboard alone (or is it that much worse now than it used to be? I don't use it much so I can't say.)
Then there is the problem that the devices themselves do not have much processing power and office suites tend to be heavy. Perhaps this is avoidable somewhat if you used a web based office suit but then web browsers are also rather heavy these days.
I've been moving to a much more unixy, open source based workflow myself and which is why I haven't looked too deeply into the above options. Much of this software avoids some of the above problems because it is very light (and so can be installed on the device itself) and is often not at all dependent on the rodent. But there are still problems:
. still low refresh rates
. android is quite limited when it comes to serious software, so one is likely to have to use something like Linux Deploy to install a unix style environment (which only adds to the overhead) to install such software.
. pdf or plain text tends to be the target format rather than Word (which may well be what you are stuck with) although I noticed WPS seems to only output doc rather than docx so perhaps you could get by with an old version of Word or light RTF editor.
Keyboards are less of a problem, the most obvious route being to use a bluetooth one, although not entirely unproblematic. See the more positive points in this thread (eg. Kwiz's posts):
https://www.mobileread.com/forums/sho...=242238&page=2
Given all the pitfalls I think you probably need some idea of what the first hand experience would be like, but I've not seen anyone post on using office productivity software on such a device. It might be too impractical and people have said as much before.
Most of the people doing this sort of thing would seem to be programmers using very light programs (as I mentioned above) on the device itself with a capacity to shift the heavier tasks to other devices. Some of the posts in the thread above and some of Seaniko7's admittedly brief posts relating to his use of Obuntu on the M92 come to mind.
I have a M96 (an Icarus Excel so somewhat crippled probably)(is there much difference from the N96? - I get the impression not from Machinogodzilla's thread) that I managed to pick up recently, quite cheaply. As I'm completing a PhD right now, I haven't really been able to test any such workflow to date as it all seems to involve a lot of work to get anything working very well. I'll get back to it in a couple of months time though as I can definitely see the need for it with everything being pushed online these days (eg. marking).