[Android Studio] newbit:
No need to sorry, I have to apologise. I had no clue about this at all. So in short, it is an emulator within an emulator which is called

a translator. Well, who had thought about that?!

Your goal is to "transfer" this arm translator capabilities from an AVD which has it already build in, to another one that doesn't?

This is bit out of the scope of rootAVD, but it is very interesting though. My first look would be into the image sources of that AVD, to see

If I can find some sort of isolated packages regarding that topic. If it is really "just" some configs plus libs, I would create a Magisk Module

for that task. But talking between architectures, I would expect that the Kernel of that engine has a lot to say as well. So there might

be some digging necessary to figure out what exactly is needed to accomplish this.

I took a little look into three running AVDs, Android 10 (Q) API 29, Android 11 (R) API 30 and Android 12 (preview rev 3) API S

generic_x86_64:/ # getprop | grep abi
[ro.odm.product.cpu.abilist]: [x86_64,x86]
[ro.odm.product.cpu.abilist32]: [x86]
[ro.odm.product.cpu.abilist64]: [x86_64]
[ro.product.cpu.abi]: [x86_64]
[ro.product.cpu.abilist]: [x86_64,x86]
[ro.product.cpu.abilist32]: [x86]
[ro.product.cpu.abilist64]: [x86_64]
[ro.vendor.product.cpu.abilist]: [x86_64,x86]
[ro.vendor.product.cpu.abilist32]: [x86]
[ro.vendor.product.cpu.abilist64]: [x86_64]

generic_x86_64_arm64:/ # getprop | grep abi
[ro.odm.product.cpu.abilist]: [x86_64,x86,arm64-v8a,armeabi-v7a,armeabi]
[ro.odm.product.cpu.abilist32]: [x86,armeabi-v7a,armeabi]
[ro.odm.product.cpu.abilist64]: [x86_64,arm64-v8a]
[ro.product.cpu.abi]: [x86_64]
[ro.product.cpu.abilist]: [x86_64,x86,arm64-v8a,armeabi-v7a,armeabi]
[ro.product.cpu.abilist32]: [x86,armeabi-v7a,armeabi]
[ro.product.cpu.abilist64]: [x86_64,arm64-v8a]
[ro.vendor.product.cpu.abilist]: [x86_64,x86,arm64-v8a,armeabi-v7a,armeabi]
[ro.vendor.product.cpu.abilist32]: [x86,armeabi-v7a,armeabi]
[ro.vendor.product.cpu.abilist64]: [x86_64,arm64-v8a]

emulator64_x86_64_arm64:/ # getprop | grep abi
[ro.odm.product.cpu.abilist]: [x86_64,arm64-v8a]
[ro.odm.product.cpu.abilist32]: []
[ro.odm.product.cpu.abilist64]: [x86_64,arm64-v8a]
[ro.product.cpu.abi]: [x86_64]
[ro.product.cpu.abilist]: [x86_64,arm64-v8a]
[ro.product.cpu.abilist32]: []
[ro.product.cpu.abilist64]: [x86_64,arm64-v8a]
[ro.system.product.cpu.abilist]: [x86_64,arm64-v8a]
[ro.system.product.cpu.abilist32]: []
[ro.system.product.cpu.abilist64]: [x86_64,arm64-v8a]
[ro.vendor.product.cpu.abilist]: [x86_64,arm64-v8a]
[ro.vendor.product.cpu.abilist32]: []
[ro.vendor.product.cpu.abilist64]: [x86_64,arm64-v8a]

I did not even notice these difference before. A quick test also showed,

that APKs build for armeabi-v7a and arm64-v8a,

could be installed and run on Android 11 (R), but not on Android 10 (Q).

APKs build for arm64-v8a could be installed and run on Android 12 (S).

But, when I extracted the busybox for armeabi-v7a, it doesn't run and gives me an error:

generic_x86_64_arm64:/data/data/com.android.shell/Magisk $ ./busybox
Error running ./busybox: couldn\'t reserve 1277952 bytes of address space at 0x8000 for "/data/data/com.android.shell/Magisk/busybox"
255|generic_x86_64_arm64:/data/data/com.android.shell/Magisk $

emulator64_x86_64_arm64:/data/data/com.android.shell/Magisk # ./busybox
/system/bin/sh: ./busybox: No such file or directory
126|emulator64_x86_64_arm64:/data/data/com.android.shell/Magisk # ls -l
total 16892
-rwxr-xr-x 1 shell shell 13116 2021-05-08 13:33 AndroidManifest.xml
drwxr-xr-x 4 shell shell 4096 2021-05-08 13:33 META-INF
-rwxr-xr-x 1 shell shell 6720493 2021-05-07 20:05 Magisk.zip
drwxr-xr-x 3 shell shell 4096 2021-05-08 13:33 assets
-rwxr-xr-x 1 shell shell 1248676 2021-05-08 13:33 busybox
-rwxr-xr-x 1 shell shell 3064400 2021-05-08 13:33 classes.dex
drwxr-xr-x 6 shell shell 4096 2021-05-08 13:33 lib
drwxr-xr-x 3 shell shell 4096 2021-05-08 13:33 org
-rwxr-xr-x 1 shell shell 2799673 2021-05-08 13:26 ramdisk.img
drwxr-xr-x 7 shell shell 24576 2021-05-08 13:33 res
-rwxr-xr-x 1 shell shell 1346756 2021-05-08 13:33 resources.arsc
-rwxr-xr-x 1 shell shell 1994828 2021-05-08 13:33 rootAVD.sh
emulator64_x86_64_arm64:/data/data/com.android.shell/Magisk #

May I ask, why you want to port that feature to a lower Android Version? It looks pretty convenient to me that it already works in Android 11 and 12.

Cheers NewBit