Interesting question, why would you want to do that?
Pools relates to, (references), the pool and fallback pools you're mining with.

dcri relates to the hardware, tuning etc, (no relation to pool, at least not that I can see).

What situation are you trying to solve here?

Note: You can very easily have multiple batch files, containing a full config set, or use the config.txt for hardware setup, (dcri etc), and use a simplified batchfile to start, (referencing config.txt and pool.txt files).

Claymore is pretty nicely architectured in that sense, multiple configuration methods, depending on your use case or preference.

Also, a note on "moving", changing architecture in such a drastic way, is generally a very bad idea, unless there is a specific showstopper bug, (not likely in a more mature package). But essentially if you do that, you have a branch, and create a legacy of shit for users.
The mature users will know the old way, and the new users will probably only know the new way.

The reality of this is, endless questions about why "it" does not work from the very same people who never read the readme.

This is still an interesting question though, can you please add some background as to why you'd want dcri in the pools.txt file?

Happy mining.