Dropdown not populated if the widget type is Tagify Select

Thank you for this wonderful module. It's working great with normal Select fields. However, I am facing issues when used with Tagify.

Problem/Motivation

When the Dependent Dropdown (child field) is a Tagify Select Widget, its not populated with options.

Steps to reproduce

1. Setup the two Dependent Fields (Field A and Field B) as instructed in the module. Make sure its working as expected with normal Select Widget.
2. In the Manage Form Display section, change the Widget of the Child field (Field B) to Tagify Select.
3. Check if the Child field (Field B) is updated/populated with options after changing the Parent Field (Field A).
4. Child field (Field B) is Empty, not populated.

Proposed resolution

To confirm if it is an issue from Tagify's side, I did a small experiment with a basic node form. I created two fields Select A and Select B whose Widgets are set to Tagify Select. I used the standard ReplaceCommand, which worked as expected. The child field is populated with the options. Since the following code is working fine with Tagify Select, we can conclude that the fix has to come from this, Dependent Fields, module.

<?php

use Drupal\Core\Ajax\AjaxResponse;
use Drupal\Core\Ajax\ReplaceCommand;

function experiments_form_node_page_form_alter(
  array &$form,
  \Drupal\Core\Form\FormStateInterface $form_state,
  string $form_id
): void {

  $form['field_select_b']['#prefix'] = "<div id='test-ajax-block'>";
  $form['field_select_b']['#suffix'] = "</div>";

  $form['field_select_a']['widget']['#ajax'] = [
    'callback' => 'just_a_test_callback',
    'event'    => 'change',
    'wrapper'  => 'test-ajax-block',
    'progress' => ['type' => 'throbber', 'message' => NULL],
  ];
}

function just_a_test_callback(array &$form, \Drupal\Core\Form\FormStateInterface $form_state): AjaxResponse {
  $form['field_select_b']['widget']['#options'] = [
    'orange'  => 'Orange',
    'apple'  => 'Apple',
    'banana'  => 'Banana',
  ];

  $renderer = \Drupal::service('renderer');
  $rendered = $renderer->render($form['field_select_b']);

  $response = new AjaxResponse();
  $response->addCommand(new ReplaceCommand('#test-ajax-block', $rendered));
  return $response;
}

So, I started digging into the module's code. The module uses a custom Ajax Command named UpdateOptionsCommand which is implemented with custom javascript at update-options-command.js. Not sure which one would be a better option.

1. Making changes to the implementation of UpdateOptionsCommand?
2. OR skipping it (UpdateOptionsCommand) when the Widget type is Tagify Select.

When the Widget type is Tagify Select, we could use ReplaceCommand maybe?

Would be grateful for any support or guidance from the maintainers.

Note: There are two other issues related to Tagify Select, but they are different. This issue addresses a different problem.